agentleFS
Sign inStart free
tmdytmdy/CodeDeck/.claude/skills/trellis-check/SKILL.md

trellis-check

Skill2 starsChanged 26 days agoMITView on GitHub

Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.

21 other projects use a version of this, 20 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    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
  • could be automatic: a setting could enforce it
  1. Common:

    Read the current task artifacts in order:

    line 21
  2. Common:

    Read the specific guideline files referenced — the index is a pointer, not the goal.

    line 37
  3. Common:

    Run the project's lint, type-check, and test commands.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 20 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

Code Quality Check

Comprehensive quality verification for recently written code. Combines spec compliance, cross-layer safety, and pre-commit checks.

Step 1: Identify What Changed

git diff --name-only HEAD
git status

Step 2: Read Task Artifacts and Applicable Specs

Read the current task artifacts in order:

  • prd.md
  • design.md if present
  • implement.md if present
python ./.trellis/scripts/get_context.py --mode packages

For each changed package/layer, read the spec index and follow its Quality Check section:

cat .trellis/spec/<package>/<layer>/index.md

Read the specific guideline files referenced — the index is a pointer, not the goal.

Step 3: Run Project Checks

Run the project's lint, type-check, and test commands. Fix any failures before proceeding.

Step 4: Review Against Checklist

Code Quality

  • Linter passes?
  • Type checker passes (if applicable)?
  • Tests pass?
  • No debug logging left in?
  • No suppressed warnings or type-safety bypasses?

Test Coverage

  • New function → unit test added?
  • Bug fix → regression test added?
  • Changed behavior → existing tests updated?

Spec Sync

  • Does .trellis/spec/ need updates? (new patterns, conventions, lessons learned)

"If I fixed a bug or discovered something non-obvious, should I document it so future me won't hit the same issue?" → If YES, update the relevant spec doc.

Step 5: Cross-Layer Dimensions (if applicable)

Skip this step if your change is confined to a single layer.

A. Data Flow (changes touch 3+ layers)

  • Read flow traces correctly: Storage → Service → API → UI
  • Write flow traces correctly: UI → API → Service → Storage
  • Types/schemas correctly passed between layers?
  • Errors properly propagated to caller?

B. Code Reuse (modifying constants, creating utilities)

  • Searched for existing similar code before creating new?
    grep -r "pattern" src/
  • If 2+ places define same value → extracted to shared constant?
  • After batch modification, all occurrences updated?

C. Import/Dependency (creating new files)

  • Correct import paths (relative vs absolute)?
  • No circular dependencies?

D. Same-Layer Consistency

  • Other places using the same concept are consistent?

Step 6: Report and Fix

Report violations found and fix them directly. Re-run project checks after fixes.

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.

Check your setup, free