Pytest Best Practices
CheckedEnforces pytest best practices like parametrization, fixtures, and clear test naming for robust and maintainable tests.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add cfircoo/claude-code-toolkit --skill pytest-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
cfircoo
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned cfircoo/claude-code-toolkit at d6264305dc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d6264305dc
- Scanned
- 5 files, 691 lines
About this skill
What it does
This skill provides guidance and best practices for writing effective tests using the pytest framework. It helps ensure test suites are maintainable, readable, and cover all critical aspects of a codebase. The skill focuses on improving testing workflows by applying established conventions and patterns within pytest.
When to use it
- Refactoring existing tests: To improve the structure and readability of an older pytest-based test suite.
- Starting a new project with pytest: To establish good testing habits from the beginning.
- Debugging failing tests: To identify common pitfalls and ensure tests are properly configured.
- Improving code coverage: To guide writing comprehensive tests that cover all critical functionality.
Key capabilities
- Provides guidance on test structure and organization.
- Offers best practices for fixture usage.
- Suggests conventions for naming tests and assertions.
- Addresses common pytest configuration issues.
Example prompts
- "How should I structure my pytest tests for a Django project?"
- "What's the best way to use fixtures in pytest to avoid duplication?"
- "Can you give me some examples of good test names using pytest?"
Tips & gotchas
This skill assumes familiarity with the basics of Python and testing concepts. While it provides guidance, a solid understanding of pytest’s core functionality is helpful for optimal results.