SkillAgentSearch skills...

trellis-check

Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks

Install / Use

npx skills add fy-agent/fyagent --skill trellis-check

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Legal

Supported Platforms

Universal

Our assessment of trellis-check

trellis-check scores 87/100 on our quality scale, 90th of 208 Legal skills we index (top 44%).

Its SKILL.md is 3.6 KB long, well organised into 15 sections with 3 code examples: a solid amount of guidance for an agent.

With 1,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so trellis-check is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

trellis-check compared with similar skills

All 4 of these similar skills score higher than trellis-check; compare them before choosing.

SkillScoreStarsUpdatedFormat
trellis-check (this skill)by fy-agent871.2k55d agoSKILL.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install trellis-check?
Run npx skills add fy-agent/fyagent --skill trellis-check. The install tabs above show the steps for each supported agent.
Which AI agents does trellis-check work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is trellis-check safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is trellis-check still maintained?
The repository was last updated about 2 months ago, so trellis-check is actively maintained.

name: trellis-check description: "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."

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.

Scope Discipline

  • [ ] Any tidying of code the task did not require?
  • [ ] Any abstraction, config or extension point added for a case that does not exist yet?
  • [ ] Any speculative fallback for a state that cannot occur?
  • [ ] Any file changed that the acceptance criteria do not mention?
  • [ ] Any workaround added at the caller instead of a fix where the behavior actually lives?

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 the same value repeats, does it represent one stable concept whose callers must change together? Extract only then — two literals that merely happen to match today should stay separate.
  • [ ] 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 every violation you find. Then:

  • Mechanical and local (lint nit, missing type, wrong import, dead branch, failing assertion) → fix in place, then re-run project checks.
  • Design or judgment (naming a shared concept, moving a module boundary, changing a public interface, reassigning where behavior lives) → record the evidence and your recommendation, and stop. Do not rewrite it silently.

If a fix would touch files outside the current task's scope, say so and stop instead of widening the change.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryLegal
Updated1mo ago
Forks135

Languages

Rust

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium