メニュー
Regression troubleshooting workflow for hook/router/memory/search failures with enforced evidence and fix validation
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/oimiragieo/agent-studio --skill troubleshooting-regressionコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Agent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field
Context management — pre-compact persistence, threshold alignment, microcompact/circuit breaker detection
Hook enhancements — updatedInput for bash safety prefixes, suppressOutput for verbose blocks, denial-based routing feedback
SKILL.md を表示中
SOC 職業分類に基づく
| name | troubleshooting-regression |
| description | Regression troubleshooting workflow for hook/router/memory/search failures with enforced evidence and fix validation |
| argument-hint | [--prompt "..."] [--log-path <path>] [--mode quick|full] |
| verified | true |
| lastVerifiedAt | "2026-02-22T00:00:00.000Z" |
| version | 1.0.0 |
| tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
| source | builtin |
| trust_score |
| 100 |
| provenance_sha | b44d6767fd4adf12 |
Use this skill when the framework appears stale, stuck, or regressed and you need deterministic diagnosis plus fix verification.
Do not declare a regression fixed without:
pnpm trace:query,pnpm trace:query --trace-id <traceId> --compact --since <ISO-8601> --limit 200).C:\\Users\\<user>\\.claude\\debug\\*.txtpnpm trace:query output for the same incident windowPrimary wrapper:
node .claude/skills/troubleshooting-regression/scripts/main.cjs --prompt "search the codebase for any issues or bugs"
pnpm trace:query --trace-id <traceId> --compact --since <ISO-8601> --limit 200
Optional direct log analysis:
node .claude/skills/troubleshooting-regression/scripts/main.cjs --log-path "C:\\Users\\<user>\\.claude\\debug\\<session>.txt"
ok: booleanlogPath: analyzed log pathfindings[]: normalized findings with severity and owner file hintsnextActions[]: concrete fix/validation actions.claude/workflows/troubleshooting-regression-skill-workflow.md.claude/tools/troubleshooting-regression/troubleshooting-regression.cjs.claude/commands/troubleshooting-regression.md# Analyze latest log
node .claude/skills/troubleshooting-regression/scripts/main.cjs --mode quick
# Analyze specific log and fail when critical findings exist
node .claude/skills/troubleshooting-regression/scripts/main.cjs --log-path "<path>" --strict
| Anti-Pattern | Why It Fails | Correct Approach |
|---|---|---|
| Making changes without reproducing failure | Can't verify the change fixed the right thing | Reproduce deterministically first, then fix |
| Fixing symptoms without root cause analysis | Problem recurs under different conditions | Use 5 Whys to trace to the root cause |
| Skipping regression suite after fix | Fix may break other functionality | Run full test suite after every change |
| Undocumented fixes | Same regression returns in future sessions | Record root cause, fix, and validation in issues.md |
| Resolving without end-to-end validation | Integration issues are missed | Validate the exact failure path end-to-end |
Before starting:
cat .claude/context/memory/learnings.md
After completing:
.claude/context/memory/learnings.md.claude/context/memory/issues.md.claude/context/memory/decisions.mdASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.