← Back to Skills Marketplace
anderskev

Pytest Code Review

by Kevin Anderson · GitHub ↗ · v1.1.1 · MIT-0
cross-platform ✓ Security Clean
157
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install pytest-code-review
Description
Reviews pytest test code for async patterns, fixtures, parametrize, and mocking. Use when reviewing test_*.py files, checking async test functions, fixture u...
README (SKILL.md)

Pytest Code Review

Quick Reference

Issue Type Reference
async def test_*, AsyncMock, await patterns references/async-testing.md
conftest.py, factory fixtures, scope, cleanup references/fixtures.md
@pytest.mark.parametrize, DRY patterns references/parametrize.md
AsyncMock tracking, patch patterns, when to mock references/mocking.md

Review gates

Work in order. Do not assert pytest-specific problems until each applicable gate passes.

  1. Scoped filesPass when: You list every test_*.py and any conftest.py you will cite; no findings for files outside that list.
  2. Async vs syncPass when: Per scoped file, you note whether it uses async def test_* / await; if yes, open references/async-testing.md before criticizing async usage.
  3. FixturesPass when: If shared setup matters, you name the conftest.py path(s) or state none; for yield fixtures, confirm cleanup exists before claiming resource leaks.
  4. patch / mocksPass when: For any patch or mock critique, you give the import path where the symbol is used (call site), or mark N/A; open references/mocking.md when mocking is central to the review.
  5. FindingsPass when: Each finding includes a file path and line(s) or test node id, not a generic rule restatement.

Review Checklist

  • Test functions are async def test_* for async code under test
  • AsyncMock used for async dependencies, not Mock
  • All async mocks and coroutines are awaited
  • Fixtures in conftest.py for shared setup
  • Fixture scope appropriate (function, class, module, session)
  • Yield fixtures have proper cleanup in finally block
  • @pytest.mark.parametrize for similar test cases
  • No duplicated test logic across multiple test functions
  • Mocks track calls properly (assert_called_once_with)
  • patch() targets correct location (where used, not defined)
  • No mocking of internals that should be tested
  • Test isolation (no shared mutable state between tests)

When to Load References

  • Reviewing async test functions → async-testing.md
  • Reviewing fixtures or conftest.py → fixtures.md
  • Reviewing similar test cases → parametrize.md
  • Reviewing mocks and patches → mocking.md

Review Questions

  1. Are all async functions tested with async def test_*?
  2. Are fixtures properly scoped with appropriate cleanup?
  3. Can similar test cases be parametrized to reduce duplication?
  4. Are mocks tracking calls and used at the right locations?
Usage Guidance
This skill appears coherent and limited to reviewing pytest test files; it requires no credentials or installs. Before enabling it, confirm you are comfortable allowing the agent access to the repository files you want reviewed (it will enumerate and read test_*.py and conftest.py). If you do not want automated agents to run this skill autonomously, keep autonomous invocation disabled for your agent or review results manually. If you need stronger assurance, inspect the SKILL.md and reference files yourself — they are bundled and readable and contain the full runtime instructions.
Capability Analysis
Type: OpenClaw Skill Name: pytest-code-review Version: 1.1.1 The skill bundle is a legitimate tool designed to guide an AI agent through reviewing Python pytest code. It contains structured instructions in SKILL.md and comprehensive reference guides in the references/ directory covering async testing, fixtures, mocking, and parametrization. There is no evidence of malicious intent, data exfiltration, or unauthorized execution; the code snippets provided are educational examples of 'good' vs 'bad' testing patterns.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
Name/description (pytest test review for async, fixtures, parametrize, mocking) align with the provided SKILL.md and reference docs. There are no unrelated env vars, binaries, or install steps that would be out-of-scope for a reviewer.
Instruction Scope
Runtime instructions focus on enumerating and analyzing test_*.py and conftest.py files and consulting the bundled reference docs. The guidance limits findings to scoped files and does not instruct reading unrelated system files, environment variables, or sending data externally.
Install Mechanism
No install spec or code files are provided — this is an instruction-only skill, so nothing is downloaded or written to disk during install.
Credentials
The skill requests no environment variables, credentials, or config paths. The analysis it prescribes operates on repository test files only, which is proportionate to its stated purpose.
Persistence & Privilege
Flags: always is false (not force-included) and model invocation is allowed (default). Neither setting is excessive for this kind of skill and the skill does not request long-term persistence or modify other skills' configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install pytest-code-review
  3. After installation, invoke the skill by name or use /pytest-code-review
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.1
- Introduced a "Review gates" section, outlining step-by-step requirements to be met before asserting pytest-specific issues. - Clarified that all findings must reference specific file paths and lines or node IDs. - Specified review process for async vs sync tests, fixtures, and mocking, with explicit criteria for each. - No changes to review checklist or quick reference content.
v1.1.0
pytest-code-review 1.1.0 - Added a detailed review checklist for pytest async tests, fixtures, parametrization, and mocking. - Introduced clear references for async patterns, fixtures, parametrize, and mocking topics. - Provided guidance on when to load specific reference materials. - Included review questions to guide thoughtful code analysis.
Metadata
Slug pytest-code-review
Version 1.1.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 2
Frequently Asked Questions

What is Pytest Code Review?

Reviews pytest test code for async patterns, fixtures, parametrize, and mocking. Use when reviewing test_*.py files, checking async test functions, fixture u... It is an AI Agent Skill for Claude Code / OpenClaw, with 157 downloads so far.

How do I install Pytest Code Review?

Run "/install pytest-code-review" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Pytest Code Review free?

Yes, Pytest Code Review is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Pytest Code Review support?

Pytest Code Review is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Pytest Code Review?

It is built and maintained by Kevin Anderson (@anderskev); the current version is v1.1.1.

💬 Comments