agentleFS
mab-gomab-go/trello-mcp/.agents/skills/verify-changes/SKILL.md

verify-changes

Skill0 starsChanged 6 months agoMITView on GitHub

Runs the project's build, test, and lint workflow and checks whether documentation needs updating. Use after completing implementation work, before committing, or when the user says "verify", "check", or "are we done".

14 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, design-spec and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 3 projects that use this

  • jornalistainclusivoSkill

    design-spec

    How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.

    Also in 3 projects that use this

  • xenitV1Skill

    bash-linux

    Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

    Also in 3 projects that use this

  • xenitV1Skill

    red-team-tactics

    Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 3 projects that use this

  • +7 more from xenitV1

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 10

    Distinctive

    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 the project's agent instructions (e.g.

    line 8
  2. Distinctive:

    After completing implementation work

    line 12
  3. Distinctive:

    Before generating a commit message

    line 13
  4. Very specific:

    Identify the verification commands: Check the project's agent instructions (AGENTS.md), Makefile, or CI config for the canonical …

    line 19
  5. Distinctive:

    Fix failures: If any step fails, diagnose and fix the issue, then re-run from the top.

    line 21
  6. Distinctive:

    Make doc updates: if needed.

    line 27
  7. Distinctive:

    Re-run verification: if doc changes touched source files (e.g.

    line 28
  8. Distinctive:

    Do not skip verification because "it's a small change." Small changes break builds too.

    line 32
  9. Distinctive:

    Do not mark verification complete if there are known failures the user has not acknowledged.

    line 33
  10. Distinctive:

    Do not run only tests without also running lint, or vice versa.

    line 34
  11. Distinctive:

    Do not silently suppress warnings or skip flaky tests without flagging them.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Verify Changes

Read the project's agent instructions (e.g. AGENTS.md) before applying this skill to ensure the correct verification commands and documentation requirements are known.

When to apply

  • After completing implementation work
  • Before generating a commit message
  • User says "verify," "check," or "are we done?"
  • User invokes /verify-changes

Procedure

  1. Identify the verification commands. Check the project's agent instructions (AGENTS.md), Makefile, or CI config for the canonical build/test/lint commands. Common patterns: make build test lint, npm test, cargo clippy && cargo test.
  2. Run them. Execute the full suite. Do not skip steps or run partial checks.
  3. Fix failures. If any step fails, diagnose and fix the issue, then re-run from the top. Repeat until clean.
  4. Check documentation. Based on what changed, determine whether project documentation needs updating:
    • New/removed files -- project structure docs
    • New utilities or helpers -- reference tables or API docs
    • New conventions established -- convention docs
    • New config or skill files -- reflect in agent instructions if they affect agent behavior
  5. Make doc updates if needed.
  6. Re-run verification if doc changes touched source files (e.g. doc comments in code, embedded docs).

Anti-patterns

  • Do not skip verification because "it's a small change." Small changes break builds too.
  • Do not mark verification complete if there are known failures the user has not acknowledged.
  • Do not run only tests without also running lint, or vice versa. Run the full suite.
  • Do not silently suppress warnings or skip flaky tests without flagging them.

Related skills

  • This is a natural prerequisite for /commit-message.
  • Include as the final item when using /make-todos to decompose work.

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.