agentleFS
ambient-codeambient-code/platform/skills/align/SKILL.md

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

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.
  • WordPressSkill

    blueprint

    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

  • NVIDIASkill

    research

    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

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

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
  1. Distinctive:

    Use the Agent tool to dispatch the convention-eval agent:

    line 45
  2. Distinctive:

    If no scope is specified, run all categories.

    line 54

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 only

User Input

$ARGUMENTS

How It Works

  1. Parse scope from $ARGUMENTS (default: full scan)
  2. Dispatch the convention-eval agent 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
  3. 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

CategoryChecksWeightKey concerns
Backend825%panic, service account misuse, error handling
Frontend825%any types, raw HTML, manual fetch
Operator720%OwnerReferences, SecurityContext, reconciliation
Runner410%async patterns, credential handling
Security720%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.

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.