align
Skill131 starsChanged 6 months agoMITView on GitHub
Run a convention alignment check across the codebase to measure adherence to documented standards. Use when you want to check health of the codebase, verify convention compliance, get a scored report, find violations, check alignment before a release, or run periodic quality scans. Triggers on: "check conventions", "alignment scan", "codebase health", "are we following our standards", "convention violations", "quality check", "how aligned are we".
16 other projects use a version of this.
Adopted by
Most recently taken up by
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- KerberosClaw/kc_ai_skillstheir own version, first seen Nov 1, 2026
- lgy1027/specflow-agent-packtheir own version, first seen Nov 1, 2026
- hmmhmmhm/aligns.mdtheir own version, first seen Oct 17, 2026
- hmmhmmhm/align.mdtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use blueprint, research and 1 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.
WordPressSkillblueprint
Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- KerberosClaw/kc_ai_skills★ 79same name
- samirpatil2000/skills★ 17same name
- hmmhmmhm/align.md★ 9same name
- hmmhmmhm/aligns.md★ 9same name
- HaipingShi/coderail★ 8same name
- JustineDevs/meta-architect★ 5same name
- lgy1027/specflow-agent-pack★ 4same name
- devjiwonchoi/skills★ 2same name
- dimsedra/skills★ 2same name
- JustineDevs/premortem★ 2same name
6 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- amber-reviewSkill
- workflowSkill
- ambient-pr-testSkill
- ambientSkill
- dev-clusterSkill
- deploySkill
- devflowSkill
- discoverSkill
- cypress-demoSkill
- frontend-developmentSkill
- grpc-devSkill
- unleash-flagSkill
- memorySkill
- pr-fixerSkill
- scaffoldSkill
- ambient-api-serverSkill
- specSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
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
- Distinctive: line 45
Use the Agent tool to dispatch the convention-eval agent:
- Distinctive: line 54
If no scope is specified, run all categories.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Convention Alignment Check
Measure codebase adherence to documented conventions. Produces a scored report across 5 categories with ~34 checks.
Usage
/align # Full codebase scan
/align backend # Backend checks only
/align frontend # Frontend checks only
/align operator # Operator checks only
/align runner # Runner checks only
/align security # Security checks onlyUser Input
$ARGUMENTSHow It Works
- Parse scope from
$ARGUMENTS(default: full scan) - Dispatch the
convention-evalagent with the scope- The agent runs in its own context window
- It loads component-level convention docs
- It runs all checks via grep/glob/bash
- It produces a scored report
- Display the report to the user
Dispatching the Agent
Use the Agent tool to dispatch the convention-eval agent:
Agent({
description: "Convention alignment check",
prompt: "You are the convention-eval agent. Read your definition at .claude/agents/convention-eval.md, then run a ${scope} convention alignment check. Scope: ${scope} (one of: full, backend, frontend, operator, runner, security). Load all context files listed in your definition, run the checks, and report findings in the standard output format with scores."
})If no scope is specified, run all categories.
Report Format
The agent produces a markdown report with:
- Overall weighted score (0-100%)
- Per-category scores (Backend, Frontend, Operator, Runner, Security)
- Pass/fail per check with file:line references
- Failures grouped by severity (Blocker > Critical > Major > Minor)
- Top 3 recommendations for improvement
Categories and Weights
| Category | Checks | Weight | Key concerns |
| Backend | 8 | 25% | panic, service account misuse, error handling |
| Frontend | 8 | 25% | any types, raw HTML, manual fetch |
| Operator | 7 | 20% | OwnerReferences, SecurityContext, reconciliation |
| Runner | 4 | 10% | async patterns, credential handling |
| Security | 7 | 20% | RBAC, token redaction, input validation |
Interpreting Results
- 90-100%: Excellent alignment. Ship with confidence.
- 70-89%: Good alignment. Address blockers before merge.
- 50-69%: Moderate alignment. Technical debt accumulating.
- Below 50%: Significant drift. Prioritize convention adherence.
Any Blocker failures should be addressed immediately regardless of overall score.
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.

