agentleFS
Sign inStart free
sonii-shivanshsonii-shivansh/CodeContext/.agents/skills/vericore-pr-verification/SKILL.md

vericore-pr-verification

Skill31 starsChanged 7 days agoMITView on GitHub

Independently review an approved Vericore change or pull request against the issue, existing contracts, tests, documentation and stated acceptance criteria.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the approved issue, feature spec and acceptance criteria.

    line 7
  2. Distinctive:

    Check compatibility: public CLI, JSON schemas, MCP tools, REST endpoints, installer/release and supported runtime.

    line 8
  3. Distinctive:

    Do not change unrelated files, approve your own work as an independent reviewer, merge, push or publish releases.

    line 13

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

Vericore PR Verification

  1. Read the approved issue, feature spec and acceptance criteria; capture the base/head SHA and exact changed files.
  2. Check compatibility: public CLI, JSON schemas, MCP tools, REST endpoints, installer/release and supported runtime.
  3. Inspect diffs, negative tests, valid alternative behavior, safety/error paths and whether docs match implementation.
  4. Execute only pre-approved safe test commands; capture exit codes and exact output excerpts. If unavailable, mark NOT RUN.
  5. Review CI checks for the exact candidate SHA. A green check does not establish semantic correctness.
  6. Report PASS/FAIL/NEEDS REVIEW per criterion with evidence and explicit limits; list risks and unresolved questions.
  7. Do not change unrelated files, approve your own work as an independent reviewer, merge, push or publish releases.

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