agentleFS
sodejmsodejm/portable-agent-repository-kit/.claude/skills/repository-check/SKILL.md

repository-check

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Run the repository-owned validation path, capture exact evidence, and separate failures, skips, and environment blockers.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Read AGENTS.md and inspect current Git state.

    line 8
  2. Distinctive:

    Run the narrow test or check that matches the change during development.

    line 9
  3. Very specific:

    Run make check before handoff unless the contract specifies a stronger gate.

    line 10
  4. Distinctive:

    Never report a pass from source inspection alone.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Repository check

  1. Read AGENTS.md and inspect current Git state.
  2. Run the narrow test or check that matches the change during development.
  3. Run make check before handoff unless the contract specifies a stronger gate.
  4. Record exact commands, exit status, meaningful results, skipped coverage, and residual risk. Sanitize paths, credentials, private data, and internal URLs.
  5. Classify each failure as a code failure, test failure, environment limitation, missing dependency, or hosted-service failure before proposing action.

Never report a pass from source inspection alone. Do not silently weaken checks or change assertions merely to obtain a green result.

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.