بنقرة واحدة
systematic-debugging
Debug failures by finding evidence and root cause before changing code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Debug failures by finding evidence and root cause before changing code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | systematic-debugging |
| description | Debug failures by finding evidence and root cause before changing code. |
Use when something fails, flakes, regresses, or behaves differently between environments.
Record the failing command or artifact inspected, the focused check that now passes, and any broader gate still needed.
Explain Topchester commands, configuration, knowledge-base behavior, skills, hooks, sessions, and troubleshooting using packaged product guidance and current workspace facts.
Configure Topchester project and user settings. Use when editing or explaining `topchester.jsonc`, `~/.config/topchester/config.jsonc`, model providers, command policy, ignore paths, hooks, project instruction files, or repo-scoped command approvals.
Review code for correctness, maintainability, security, and project fit.
Split larger work into ordered, verifiable implementation slices.
Quickly map an unfamiliar repository before changing it.
Add or tighten tests before implementing a behavior change.