trellis-review-twostage
bycoldwateryi· 14 skills
Before marking a Trellis subtask complete after self-check all green, conduct two-stage code review: mechanically check spec compliance (against PRD acceptance criteria/decision table/forbidden/file manifest/mount points), then code quality review (against .trellis/spec/guides engineering standards and design discipline). Used in Codex / Claude Code team collaboration scenarios, especially when implementation is by a small-parameter model like qwen3.6 35b—small models reviewing their own code is unreliable, Stage 2 should escalate to strong model; critical issues block completion.
How to install trellis-review-twostage?
coldwateryi/trellis-skills/trellis-review-twostage
$npx -y skills add coldwateryi/trellis-skills --skill trellis-review-twostageInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/coldwateryi/trellis-skills" --skill "coldwateryi/trellis-skills/trellis-review-twostage"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/coldwateryi/trellis-skills" that are relevant to the current task. Run `npx skills add "https://github.com/coldwateryi/trellis-skills"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
