agentleFS
xsovad06xsovad06/sova/.agents/skills/sova-test/SKILL.md

sova-test

Skill3 starsChanged 5 days agoApache-2.0View on GitHub

Run tests and linter for the current project until all issues are fixed.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run tests and linter, fixing issues iteratively until everything passes.

    line 8
  2. Distinctive:

    If unclear, check git diff --name-only to see which modules have changes.

    line 15
  3. Very specific:

    Run the project's lint command: make lint

    line 19
  4. Very specific:

    Run the project's test command: make test

    line 28
  5. Very specific:

    After tests pass: Run the sova-review skill to self-review before pushing

    line 47
  6. Very specific:

    Full workflow: Use the sova-develop-full skill for the complete develop-test-review-pr cycle

    line 48
  7. Distinctive:

    Always fix linter issues before running tests

    line 52
  8. Distinctive:

    After fixing issues, re-run to verify the fix

    line 53
  9. Distinctive:

    NEVER use emojis in any output

    line 56

≈ “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

Test Runner

Run tests and linter, fixing issues iteratively until everything passes.

Instructions

Step 1: Identify the Scope

Determine what to test from the arguments provided when this skill is invoked or the current directory. If unclear, check git diff --name-only to see which modules have changes.

Step 2: Run Linter

Run the project's lint command: make lint

If linter fails:

  • Analyze the errors
  • Fix the code issues
  • Re-run until it passes

Step 3: Run Tests

Run the project's test command: make test

If tests fail:

  • Analyze the test failures
  • Fix the code or tests as needed
  • Re-run until they pass

Step 4: Scout Check

While fixing test or lint failures, scan each touched file for pre-existing issues: flaky test patterns, stale imports, dead code. Fix them alongside the failures. Keep scout fixes small and low-risk.

Step 5: Iterate

Repeat Steps 2-4 until both linter and tests pass completely.

Cross-References

  • After tests pass: Run the sova-review skill to self-review before pushing
  • Full workflow: Use the sova-develop-full skill for the complete develop-test-review-pr cycle

Rules

  • Always fix linter issues before running tests
  • After fixing issues, re-run to verify the fix
  • Continue iterating until both pass
  • Report final status when everything is green
  • NEVER use emojis in any output

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.