What is trellis-check?

A quality-check workflow for code that has recently been written or changed. It compares the work with project requirements and runs checks such as linting, type-checking, and tests.

Use it before committing code to review changed files, read the relevant project rules, run automated checks, and inspect data flow across application layers.

It helps catch broken behavior, missing tests, unused debugging code, and differences between the implementation and the project specification before a commit.

How yuqie6/ProductFlow configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to yuqie6/ProductFlow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/yuqie6/ProductFlow/main/.agents/skills/trellis-check/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/yuqie6/ProductFlow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-check/github.svg)](https://agentmods.dev/skills/yuqie6/productflow/trellis-check)

Your own site

<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-check"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-check"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 649 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.00649
Opus 5	$0.00027	$0.00324
Sonnet 5	$0.00011	$0.00130
Haiku 4.5	$0.00005	$0.00065

Measured 10d ago against content hash b21ff04b7680, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

trellis-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

trellis-check — 100% identical, 2 lines differ
trellis-check — 100% identical, 2 lines differ

.agents/skills/trellis-check/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

python3 ./.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?

Read the full file on GitHub · 99 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 99 lines · 54 tokens per session scan A b21ff04b7680

Subscribe to this mod's changes

trellis-check is a skill published in the GitHub repository yuqie6/ProductFlow (302 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 649 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review E-commerce Legal and compliance React Testing ai fastapi productflow self-hosted

gstack-review

A set of review modes that examines development work from product, engineering, security, quality-assurance, and release perspectives.

djblack1209-coder/OpenClaw-Bot · 35 tokens

superpowers-workflow

A structured software-development workflow for turning a request into a reviewed change. It moves through brainstorming, a written plan, test-driven development (TDD), code review, and final checks; TDD means writing a failing test before the code that makes it pass.

djblack1209-coder/OpenClaw-Bot · 45 tokens

ProductFlow: Skill for Claude Code