analyze-cc-feature
Reverse engineer and analyze a specific feature in Claude Code's source. Use when the user wants to understand how a Claude Code feature works internally, or when asked to analyze Claude Code internals.
npx skills add majiayu000/claude-skill-registry --skill skill-prajwalsrinvas-claude-code-reverse --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.
# Analyze Claude Code Feature Reverse engineer a specific feature in Claude Code's source code. **Terminology note**: Claude Code's `cli.js` is **minified** (whitespace removed, identifiers shortened for size), NOT **obfuscated** (intentionally made hard to read with control flow flattening, string encryption, etc.). webcrack's `--no-deobfuscate` flag is used because there is no obfuscation to reverse. The output file is called `deobfuscated.js` by webcrack convention, but it is more accurately "unminified" source. **IMPORTANT**: Use the task list (TaskCreate/TaskUpdate) to track progress through the pipeline. Create all tasks upfront, then work through them sequentially, marking each in_progress when starting and completed when done. ## Pipeline Create these tasks at the start: 1. **Acquire source** — Download and extract cli.js from npm 2. **Unminify** — Run webcrack + prettier to produce readable source 3. **Locate the feature** — Search for anchor strings to find the code 4. **Extract & annotate** — Pull out the feature's code, rename identifiers inline 5. **Analyze** — Document what the feature does step by step 6. **Write report** — Produce a markdown report with evidence 7.
- Pipeline
- Step 1: Acquire source
- Step 2: Unminify
- Step 3: Locate the feature
- Step 4: Extract & annotate
- Step 5: Analyze
- Step 6: Report
- Step 7: Self-reflect
- Command types
- How commands are dispatched
- React/Ink components
- Common patterns
- Important notes
bash ~/.claude/skills/analyze-cc-feature/scripts/extract-cli.sh bash ~/.claude/skills/analyze-cc-feature/scripts/unminify.sh
What does the analyze-cc-feature skill do?
Reverse engineer and analyze a specific feature in Claude Code's source. Use when the user wants to understand how a Claude Code feature works internally, or when asked to analyze Claude Code internals.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill skill-prajwalsrinvas-claude-code-reverse --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.