ds-fix
This skill should be used when the user asks to 'fix analysis', 'wrong results', 'notebook error', 'reviewer feedback', 'data changed', 'debug notebook', or needs mid-analysis course-correction for wrong results, notebook errors, or data changes.
npx skills add majiayu000/claude-skill-registry --skill ds-fix --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
**Announce:** "Using ds-fix for mid-analysis course correction." ## Session Resume Detection Before starting, check for an existing handoff: 1. Check if `.planning/HANDOFF.md` exists 2. **If found:** Read it and present to user: - Show the phase, task progress, and Next Action from the handoff - Ask: "Resume from handoff, or start fresh?" - If resume: skip to the recorded phase - If fresh: proceed with diagnosis 3. **If not found:** Proceed normally with Step 1 (Load Context) ## Where This Fits ``` /ds (entry) → brainstorm → plan → implement → review → verify ↑ /ds-fix (midpoint) ─────────────────┘ ``` This is the re-entry point. Jump back into a DS workflow that needs fixing. <EXTREMELY-IMPORTANT> ## The Iron Law of DS Editing **DIAGNOSE BEFORE FIXING. This is not negotiable.** Before changing ANY analysis code, you MUST: 1. Load the workflow context 2. Identify WHAT is wrong (specific, not vague) 3. Identify WHY it's wrong (root cause) 4. Only THEN fix it (with output-first verification) **If you're about to change code without diagnosing first, STOP.** </EXTREMELY-IMPORTANT> ### Drive-Aligned Framing **Skipping diagnosis is NOT HELPFUL — guessing at a root cause wastes the user'
- Session Resume Detection
- Where This Fits
- The Iron Law of DS Editing
- Drive-Aligned Framing
- Drive-Aligned Framing (Consequences)
- Rationalization Table
- Red Flags - STOP Immediately If You Think:
- Step 1: Load Context
- SAS Project Detection
- Context Monitoring
- Step 2: Diagnose
- Diagnostic Routing Flowchart
- Step 3: Fix by Category
- Runtime Error → Debug Protocol
What does the ds-fix skill do?
This skill should be used when the user asks to 'fix analysis', 'wrong results', 'notebook error', 'reviewer feedback', 'data changed', 'debug notebook', or needs mid-analysis course-correction for wrong results, notebook errors, or data changes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ds-fix --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.