standards-spec-review
Skill2 starsChanged 11 days agoNo licenceView on GitHub
Two-axis review of the changes since a fixed point (commit, branch, tag, merge-base, or the working tree) on Standards (does the code follow this repository's documented coding standards, design documents, and the smell baseline?) and Spec (does the code do what the originating issue or specification asked for?), each run by a fresh independent agent and reported side by side without merging or reranking. Use when the user asks to review a branch, a PR, work in progress, "review since X", "is this built right and is it the right thing", or when another LANYANT skill calls for a standards-and-spec review of a diff. Not for hunting runtime bugs by breaking the change (use adversarial-review) or for full system verification with executed scenarios (use system-verification).
In this repository28 other files it gives its agents.
- adversarial-reviewSkill
- ask-ericSkill
- bug-diagnosisSkill
- business-discoverySkill
- codebase-investigationSkill
- decision-mappingSkill
- delivery-planningSkill
- delivery-proofSkill
- engineering-principlesSkill
- feature-implementationSkill
- idea-assessmentSkill
- issue-triageSkill
- multi-agent-deliverySkill
- performance-investigationSkill
- pr-deliverySkill
- process-improvementSkill
- project-environmentSkill
- project-maintenanceSkill
- project-principlesSkill
- project-releaseSkill
- refactoringSkill
- session-continuitySkill
- system-verificationSkill
- technical-designSkill
- technical-writingSkill
- test-driven-developmentSkill
- verification-harnessSkill
- workflow-prototypeSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.