mirror of
https://github.com/secondsky/claude-skills.git
synced 2026-09-18 19:54:22 +08:00
secondsky
c1afc6db8b
BREAKING CHANGE: All plugin paths changed from nested to flat structure
Problem:
- Only 11 out of 169 skills appeared in Claude Code's system prompt
- v3.1.0 updated marketplace.json but didn't migrate directory structure
- Mismatch: marketplace expected `./plugins/skill-name` but files were at
`./plugins/category/skills/skill-name`
Solution:
- Moved all 169 skills from `plugins/*/skills/*` to `plugins/*` (flat)
- Removed 66 empty category directories (api, cloudflare, testing, etc.)
- Updated marketplace.json with correct flat paths (all 169 entries)
- Updated scripts to work with flat structure:
- generate-marketplace.sh: removed nested loop logic
- sync-plugins.sh: simplified to single loop
- Added flatten-plugin-structure.sh migration tool
Migration Details:
- Used git mv to preserve history for all 169 skills
- Handled name collisions via temporary directories
- Validated: 0 errors, 169 skills successfully migrated
Results:
- ✅ All 169 skills at `plugins/*/` level
- ✅ marketplace.json: 169 valid entries
- ✅ No nested skills/ directories remain
- ✅ Scripts updated and tested
This completes the migration started in v3.1.0 (commit 677abf8) and
resolves skill discovery issues.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
Systematic Debugging Skill
Four-phase debugging framework ensuring root cause investigation before attempting fixes.
Overview
This skill enforces a disciplined approach to debugging that prioritizes understanding over quick fixes. Random fixes waste time and create new bugs. Quick patches mask underlying issues. The core principle: ALWAYS find root cause before attempting fixes.
The Four Phases
- Root Cause Investigation - Read errors, reproduce, check changes, gather evidence
- Pattern Analysis - Find working examples, compare against references, identify differences
- Hypothesis and Testing - Form single hypothesis, test minimally, verify
- Implementation - Create failing test, implement single fix, verify solution
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
When to Use
- ANY technical issue (test failures, bugs, unexpected behavior)
- Under time pressure (when guessing is tempting)
- "Just one quick fix" seems obvious
- Previous fix didn't work
- You don't fully understand the issue
Red Flags - STOP
- "Quick fix for now, investigate later"
- "Just try changing X and see if it works"
- "It's probably X, let me fix that"
- Proposing solutions before tracing data flow
- "One more fix attempt" (when already tried 2+)
Auto-Trigger Keywords
- debugging methodology
- root cause investigation
- systematic debugging
- bug investigation
- test failure analysis
- scientific debugging
- evidence-based fixes
- hypothesis testing
Source
Adapted from mrgoonie/claudekit-skills