What is trellis-check?

A broad code-quality review workflow for recently changed code. It checks requirements, formatting, types, tests, data flow, reuse, and consistency across project layers.

Use it after implementing changes or during a long task to inspect the diff, read applicable specifications, run project checks, and review the result against quality gates.

It gathers the checks needed before committing and can reveal problems that a single test or linter would miss.

How tincopper/neeko configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to tincopper/neeko. 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/tincopper/neeko/main/.agents/skills/trellis-check/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tincopper/neeko

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/tincopper/neeko/trellis-check.svg)](https://agentmods.dev/skills/tincopper/neeko/trellis-check)

Your own site

<a href="https://agentmods.dev/skills/tincopper/neeko/trellis-check"><img src="https://agentmods.dev/badge/skills/tincopper/neeko/trellis-check.svg" alt="Measured on agentmods" 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 989 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.00989
Opus 5	$0.00027	$0.00495
Sonnet 5	$0.00011	$0.00198
Haiku 4.5	$0.00005	$0.00099

Measured 8d ago against content hash c5bca5499ae9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 8d 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.

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

How it starts

The opening of the file, as written. The whole thing — 110 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?

Review Gates (Neeko-specific)

Cross-platform shell: any ExecTarget::Local path uses cmd /c on Windows and sh -c on Unix via #[cfg]? No unconditional sh -c / bash -lc on local paths?
Blocking I/O isolation: async Commands use spawn_blocking for std::fs::*, std::process::Command, or PTY blocking reads? No blocking I/O on Tokio worker threads?
IPC payload size: single Command return under 2MB? Large text (diff, PTY buffer) uses binary stream or pagination?
Event name constants: Tauri event strings defined as constants on Rust side, referenced (not re-hardcoded) on frontend?
Skinny Commands: #[tauri::command] only does param validation + dispatch? No business logic (Git/SSH/PTY) inlined?
if-let nesting: no 3+ level if let chains? Flattened to match? Conversely, no over-engineered match with _ => {} for a single Happy Path?
Path safety: frontend-supplied paths canonicalize()d before use? No fs:allow-all / shell:allow-all in capabilities?
Slim mod.rs: mod.rs only has mod declarations and pub use? Business logic extracted to services.rs / manager.rs / types.rs?

Read the full file on GitHub · 110 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

SKILL.md.backup 1.2 KB

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.

8d ago First seen · 110 lines · 54 tokens per session scan A c5bca5499ae9

Subscribe to this mod's changes

trellis-check is a skill published in the GitHub repository tincopper/neeko (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 54 tokens to every session and 989 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-31.

Claude Code Code review Testing agent agentic-ai agents dap grok

sage-review

Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.

kirodotdev/KiroCrew · 68 tokens

writing-tests

How to write a Kiro Crew backend test that has NO side effects and does not flake. Use when adding, editing, reviewing, or debugging a pytest test in the Kiro Crew source repo: which conftest is under your file, what leaks (temp dirs, the real data home, /.kiro, cron, threads, child processes), how to tell which of…

kirodotdev/KiroCrew · 123 tokens

pod-e2e

ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Runs end-to-end tests (backend API + frontend Playwright) for a Kiro Crew feature worktree against an ISOLATED throwaway pod…

kirodotdev/KiroCrew · 147 tokens

learn-from-sage

Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.

kirodotdev/KiroCrew · 56 tokens

ai-discover

Parallel discovery of performance hotspots (perf track) and failure surfaces (bug track) for the auto-improvement loop. Fans out one subagent per hot-path area or failure surface; each returns ONE concrete, behavior-preserving fix candidate (perf) or a reproducing test plus fix (bug). Discovery only — no code changes…

kirodotdev/KiroCrew · 75 tokens

relay-80-100-workflow

Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, mandatory sequential Claude-then-Codex fresh-eyes review/fix loops…

AgentWorkforce/relay · 121 tokens

neeko: Skill for Claude Code