analyzing-feature-implementations
Archived skill guidance for analyzing-feature-implementations.
npx skills add majiayu000/claude-skill-registry --skill analyzing-feature-implementations --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.
--- name: analyzing-feature-implementations description: Analyzes an existing software feature implementation. ``` # Analyzing Feature Implementations This skill produces a structured, LLM-oriented implementation report for cross-project comparison, tradeoff analysis, and improvement recommendations. Use when documenting current feature internals, comparing similar features across repositories, or preparing inputs for LLM-based design review. ## Workflow 1. Resolve feature name -> kebab-case. 2. Discover implementation surface: - Identify entrypoints, routes/handlers, core service objects, and integration points. 3. Build "Code map": - List primary files and the key identifiers in each. 4. Trace flows: - Typical happy path + 2–3 important edge/error paths. 5. Extract interfaces and contracts: - API schema, request/response, events, DB schema, config. 6. Identify tradeoffs: - What the implementation optimizes for and what it sacrifices. 7. Writes a report to doc/feature-description if folder does not exist create one.
- Workflow
What does the analyzing-feature-implementations skill do?
Archived skill guidance for analyzing-feature-implementations.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-feature-implementations --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.