feat(skill): add /drt-troubleshoot — full top-to-bottom diagnostic checklist (closes #369)#631
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ecklist (closes #369) Fifth user-facing skill, complementary to /drt-debug: - **/drt-debug** is reactive — the user has a specific error message and wants it fixed via known-pattern matching. - **/drt-troubleshoot** is for vague symptoms — "drt isn't working", a sync that silently does nothing, results that look wrong, or verifying a fresh setup end-to-end. It walks the setup top to bottom as a 7-layer isolation checklist — environment → profile/credentials → connectivity → config validity → dry-run → first real run → post-sync correctness. Each layer has a "✅ green when" gate and a "🔴 common failures" list, so the first failing layer localises the problem, then it hands off to /drt-debug for the specific fix. The skill references the current CLI surface throughout (drt doctor, drt validate, drt run --dry-run --diff, --cursor-value, tojson_safe, drt test), so it lands already aligned with v0.7+ rather than needing the catch-up the other four skills just went through (#625-#628). Wiring: - skills/drt/skills/drt-troubleshoot/SKILL.md (new) - .claude/commands/drt-troubleshoot.md (via make sync-skills) - skills/drt/.claude-plugin/plugin.json description → 5-skill set - README.md + README.ja.md skill tables → 5 rows - CHANGELOG [Unreleased] → Added make check-skills clean, make check-drift exits 0. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Keeps `make check-i18n` green after the skill-table addition. The marker was already lagging from #630's merge (recorded e1b1d15, base moved to 3f968f6); this resyncs it to the current README.md tip. Content is in sync — both skill tables carry the 5-skill set. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
masukai
force-pushed
the
feat/drt-troubleshoot-skill
branch
from
f3246df to
b24a4e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fifth user-facing Claude Code skill, complementary to
/drt-debug. Closes #369./drt-debug/drt-troubleshootHow it works
/drt-troubleshootwalks the setup top to bottom as a 7-layer isolation checklist. Each layer has a "✅ green when" gate and a "🔴 common failures" list — proceed only when the current layer is green, so the first failing layer localises the problem:drt doctordrt validate+drt listdrt run --dry-run [--diff](the key step for "runs but data looks wrong")drt run --verbose+drt statusdrt testOnce the failing layer is found, it hands off to
/drt-debugfor the specific fix.Already current
The skill references the v0.7+ CLI surface throughout (
drt doctor,drt validate,drt run --dry-run --diff,--cursor-value,tojson_safe,drt test), so it lands already aligned — no catch-up needed unlike the refresh the other four skills just went through (#625–#628).Wiring
skills/drt/skills/drt-troubleshoot/SKILL.md(new).claude/commands/drt-troubleshoot.md(viamake sync-skills)skills/drt/.claude-plugin/plugin.jsondescription → 5-skill set[Unreleased] → AddedTest plan
make check-skills—.claude/commands/drt-troubleshoot.mdmatches SKILL.mdmake check-drift— exits 0 (new skill doesn't break the audit)make check-i18n— README.ja in sync🤖 Generated with Claude Code