agentleFS
Sign inStart free
Atiqul-IslamAtiqul-Islam/graphcrew/.claude/skills/spec-test/SKILL.md

spec-test

Skill0 starsChanged 8 months agoMITView on GitHub

Run BDD tests for a spec and classify results as RED/GREEN/BROKEN

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. HHU3637kr/skills★ 146same name
    2. anyoneanderson/agent-skills★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run pytest-bdd tests for a specific spec and classify the results.

    line 8
  2. Very specific:

    If missing, suggest running /spec-compile <module-name> first

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

spec-test

Run pytest-bdd tests for a specific spec and classify the results.

Usage

/spec-test <module-name>

Process

  1. Check files exist:
    • tests/features/<module-name>.feature
    • tests/steps/test_<module-name>_steps.py
    • If missing, suggest running /spec-compile <module-name> first
  2. Run tests:
    cd /c/Users/iatiq/Documents/dev/personal/health_app/graphcrew
uv run pytest tests/steps/test_<module-name>_steps.py -v --tb=short 2>&1
  3. Classify results:
    • RED — Tests fail with NotImplementedError or assertion errors (expected for new specs)
    • GREEN — All tests pass (implementation complete)
    • BROKEN — Tests fail with import errors, syntax errors, or infrastructure issues (fix before proceeding)
  4. Report classification + summary of failures (if any)

Rules

  • RED is the expected state after /spec-compile — it means tests are correctly testing unimplemented behavior
  • GREEN means the implementation satisfies the spec
  • BROKEN means the test infrastructure itself has issues — these must be fixed before continuing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free