Trellis Debug Systematic
When a test should be green but stays red, or a self-check command fails during Trellis subtask implementation/verification, use this non-deviable rigid script for systematic root-cause pinpointing and minimal fix. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—small models quickly spiral out of control when debugging freely; this skill uses "one change at a time, must re-run after change, no guessing" iron rules to lock it on a narrow path with defensive regression checks.
Install
npx skills add coldwateryi/trellis-skills --skill trellis-debug-systematicgit clone --depth 1 https://github.com/coldwateryi/trellis-skills.git /tmp/trellis-skills
mkdir -p ~/.claude/skills
cp -r /tmp/trellis-skills/trellis-debug-systematic ~/.claude/skills/trellis-debug-systematicPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Trellis Systematic Debugging (Rigid Script) ## Overview Take over a failing test or self-check command, fix it in 4 fixed steps: pin failure signal → pinpoint → single-hypothesis verification → minimal fix + regression. This skill exists to **prevent (especially small models) from changing things everywhere and making it worse while debugging**—so it's a **numbered script + iron rules**, not suggestions. Trigger: A test in `trellis-implement-tdd`'s RED-GREEN loop should be green but stays red, or `prd.md` self-check command fails, and the cause is not obvious. Record the debugging trail in the fixed task-local file `<task-dir>/debug-report.md`. Create it from `references/debug-report-template.md` on the first debugging incident, then append a new session block for each later incident. Do not edit the template under the skill directory. ## Constraints (Iron Rules) - **One change at a time**. After changing, immediately re-run that failing command, then decide next step. - **Must re-run original failing command after change**. No re-run = no verification. - **No guessing**. Pinpointing uses only "read stack / binary-comment / add one log line" three tricks to narrow the range, not imagination-based code changes. - **Don't touch files outside file manifest / forbidden list**. When suspecting root cause is out of scope, stop and report—don't autonomously spread modifications.
Details
- Skill name
trellis-debug-systematic- Repository
- coldwateryi/trellis-skills
- Path
trellis-debug-systematic/SKILL.md- License
- MIT
- Repo updated
- 3 July 2026
FAQ
What does the Trellis Debug Systematic skill do?
When a test should be green but stays red, or a self-check command fails during Trellis subtask implementation/verification, use this non-deviable rigid script for systematic root-cause pinpointing and minimal fix. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—small models quickly spiral out of control when debugging freely; this skill uses "one change at a time, must re-run after change, no guessing" iron rules to lock it on a narrow path with defensive regression checks.
How do I install the Trellis Debug Systematic skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add coldwateryi/trellis-skills --skill trellis-debug-systematic. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Trellis Debug Systematic popular?
It lives in coldwateryi/trellis-skills, which has 44 GitHub stars and 1 forks.
Related skills
Trellis Debug Systematic Zh
44coldwateryi/trellis-skills
当 Trellis 子任务实现/验证过程中测试该绿不绿、或自检命令失败时,用一段不可偏离的刚性脚本做系统化根因定位与最小修复。用于 Codex / Claude Code 等驱动 qwen3.6 35b 这类小参数模型调试时——小模型一旦自由发挥就会到处乱改,本技能用"一次只改一处、改完必重跑、禁止猜"的铁律把它锁在窄路径上,并带防御性回归检查。
Trellis Delivery Controller
44coldwateryi/trellis-skills
Trellis requirements-to-delivery entrypoint and workflow controller. Use when the user wants to invoke one Trellis skill that detects the current stage and routes work across requirements analysis, MVP task planning, post-MVP gap audit, delivery loop, TDD implementation, systematic debugging, two-stage review, and final acceptance. Coordinates trellis-zero-to-mvp, trellis-mvp-to-delivery, trellis-implement-tdd, trellis-debug-systematic, and trellis-review-twostage while enforcing safety gates.
Trellis Delivery Controller Zh
44coldwateryi/trellis-skills
Trellis 需求交付总入口和流程控制器。用于用户希望只调用一个 Trellis skill 自动判断当前阶段,并在需求分析、MVP 任务规划、MVP 后差距审计、交付 loop、TDD 实现、系统调试、双阶段评审和最终验收之间进行路由、推进和安全门控制的场景。适合基于 trellis-zero-to-mvp-zh、trellis-mvp-to-delivery-zh、trellis-implement-tdd-zh、trellis-debug-systematic-zh 和 trellis-review-twostage-zh 形成端到端交付闭环。
Backstage Backend Plugin
23rothenbergt/backstage-agent-skills
Build Backstage backend plugins and modules with createBackendPlugin: DI, httpRouter, secure-by-default auth, Knex DB, scheduler, testing, extension points. Use for APIs, modules, and background jobs.
Trellis Review Twostage Zh
44coldwateryi/trellis-skills
在 Trellis 子任务自检全绿、标记完成之前,做两阶段代码评审:先机械核对规范符合(对照 PRD 验收标准/决策表/禁止事项/文件清单/挂载点),再做代码质量评审(对照 .trellis/spec/guides 的工程规范与设计纪律)。用于 Codex / Claude Code 等团队协作场景,尤其当实现由 qwen3.6 35b 小模型完成时——小模型评审自己的代码不可靠,Stage 2 应升级到强模型;critical 问题阻断完成。
Use Dom
49robinebers/skills
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.