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
- juraj-blahunka/skillstheir own version, first seen Nov 16, 2026
- tapiotorsti/torsti-tapiola-websitetheir own version, first seen Nov 15, 2026
- mab-go/xmind-mcpedited, first seen Nov 8, 2026
- FilenCloudDienste/filen-rstheir own version, first seen Oct 9, 2026
- vudovn/ag-kittheir own version, first seen Oct 8, 2026
- idaholab/moosetheir own version, first seen Oct 8, 2026
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.
SKB3002Skillintelligent-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
jornalistainclusivoSkilldesign-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
xenitV1Skillbash-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
xenitV1Skillred-team-tactics
Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.
Also in 3 projects that use this
xfstudioSkillrust-pro
Master Rust 1.75+ with modern async patterns, advanced type system
Also in 3 projects that use this
- +7 more from xenitV1
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- mab-go/xmind-mcp★ 926% same
Wrote their own version · 13
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- foru17/clash-master★ 4.4ksame name
- foru17/neko-master★ 4.4ksame name
- idaholab/moose★ 2.4ksame name
- h0x91b/dev-3.0★ 333same name
- FilenCloudDienste/filen-rs★ 106same name
- 26zl/universal-agent-skills★ 3same name
- zzfancitizen/agent-skills-self-learning-sample★ 3same name
- gillkyle/skills★ 1same name
3 more not listed
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-questionsSkill
- commit-messageSkill
- make-todosSkill
- review-planSkill
- smoke-testSkill
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
- Distinctive: line 8
Read the project's agent instructions (e.g.
- Distinctive: line 12
After completing implementation work
- Distinctive: line 13
Before generating a commit message
- Very specific: line 19
Identify the verification commands: Check the project's agent instructions (AGENTS.md), Makefile, or CI config for the canonical …
- Distinctive: line 21
Fix failures: If any step fails, diagnose and fix the issue, then re-run from the top.
- Distinctive: line 27
Make doc updates: if needed.
- Distinctive: line 28
Re-run verification: if doc changes touched source files (e.g.
- Distinctive: line 32
Do not skip verification because "it's a small change." Small changes break builds too.
- Distinctive: line 33
Do not mark verification complete if there are known failures the user has not acknowledged.
- Distinctive: line 34
Do not run only tests without also running lint, or vice versa.
- Distinctive: line 35
Do not silently suppress warnings or skip flaky tests without flagging them.
“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.
Files
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
- 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. - Run them. Execute the full suite. Do not skip steps or run partial checks.
- Fix failures. If any step fails, diagnose and fix the issue, then re-run from the top. Repeat until clean.
- 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
- Make doc updates if needed.
- 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-todosto decompose work.
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
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.

