Claude skill
Senior Debugging
Senior Debugging is a Claude skill in the SeniorOS plugin. Use when a test, build or runtime behavior fails, a feature regressed, behavior is flaky, a previous fix did not hold, or a report of wrong output or data comes in, even one that names the function…
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Use when a test, build or runtime behavior fails, a feature regressed, behavior is flaky, a previous fix did not hold, or a report of wrong output or data comes in, even one that names the function to fix. Not for explaining code that works or reviewing a change without a reported failure.
The skill's instructions (about 1,068 words) cover:
- Process
- Regression check
- When fixes keep failing
- Red flags
- Exit criteria
How to use it
- Senior Debugging comes inside the SeniorOS plugin, so you get it by installing that plugin, along with its 5 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose senior-debugging. In Claude Code and Cowork, type:/senioros:senior-debugging
Source
- Plugin
- SeniorOS
- SKILL.md
- View on GitHub
- Repo stars
- 3
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in SeniorOS
- Senior EngineeringUse when a coding task changes behavior, spans several files, or touches risky surfaces such as auth, data, migrations, public APIs, CI or deployment.
- Senior FinishUse right before saying a substantive change is done, fixed, passing or ready, and before committing, opening a pull request or handing it off.
- Senior Project IntelligenceUse when asked to set up or refresh the project memory in `.senior/`, after a material architecture or stack change, or when sessions keep rediscovering the same project facts.
- Senior Skill AuthoringUse when creating a new agent skill, or changing an existing skill's trigger, process, boundaries or evals.
- Senior Code ReviewUse when asked to review a diff, branch or pull request, or before merging a change of medium risk or higher, including agent-generated code.