Claude Cursor Skill

pytest-triage

Diagnoses failing pytest runs from the output the user pastes or the last local run. Use when tests fail and the cause is unclear; not for writing new tests.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-bench_judge_corpus_units_clean-02_.claude_skills_pytest-triage-ca967ad.zip · 0 KB
Part of goldziher/ai-rulez — 151 skills

Install

skills CLI npx skills add https://github.com/Goldziher/ai-rulez/tree/main/bench/judge/corpus/units/clean-02/.claude/skills/pytest-triage
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart
Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Pytest triage

  1. Run pytest -x -q --tb=short unless the user pasted output.
  2. Find the first failing test and read the test and the code it calls.
  3. Match the failure against references/common-failures.md.
  4. Report the likely cause in two sentences and propose a fix. Do not edit files unless the user asks.
Files (ai-rulez)
  • references
    • common-failures.md 257 B
      # Common failures
      
      - `fixture 'x' not found`: the fixture is defined in a conftest outside the test's directory.
      - `ImportError` only under pytest: the package is not installed in editable mode.
      - Order-dependent failure: a test mutates module-level state.
      
  • SKILL.md 520 B
    ---
    name: pytest-triage
    description: "Diagnoses failing pytest runs from the output the user pastes or the last local run. Use when tests fail and the cause is unclear; not for writing new tests."
    ---
    
    # Pytest triage
    
    1. Run `pytest -x -q --tb=short` unless the user pasted output.
    2. Find the first failing test and read the test and the code it calls.
    3. Match the failure against `references/common-failures.md`.
    4. Report the likely cause in two sentences and propose a fix. Do not edit files unless the user asks.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related