agentsclimarketplace
Sign in

Codebase analysis

Skill MiaoY0uShan/FP/install/opencode/fp/skills/codebase-analysis

Codebase analysis and impact mapping. Use when reviewing, modifying, or understanding user code where the blast radius spans multiple files. Provides code-review-graph MCP integration and grep-fallback protocols for computing change impact.From its SKILL.md

Install
npx -y skills add MiaoY0uShan/FP --skill codebase-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.1 KB, 210 tokens by cl100k_base, as published. Nobody here has run it

FP Codebase Analysis

Prefer code-review-graph MCP when available. Start with get_minimal_context_tool. Fall back to grep-based discovery when MCP is unavailable.

MCP Route

  1. get_minimal_context_tool (~100 tokens) → community names and entry points
  2. detect_changes_tool → risk-scored functions, affected flows, test gaps
  3. get_impact_radius_tool → blast radius
  4. get_architecture_overview_tool → hub/bridge nodes
  5. semantic_search_nodes_tool → semantic queries

Load ../templates/code-review-graph-mcp-contract.md for the full 30-tool map.

Grep Fallback

  1. git diff → extract changed symbols
  2. grep -rn for callers/importers
  3. Glob for test files
  4. Mark source: grep-fallback in impact map

Load ../templates/codebase-impact-map.md for the output template.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most architecture codebase skills give in 210 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • start with get_minimal_context before any other graph tool
  • use code-review-graph MCP when available
  • fall back to grep when MCP is unavailable
  • extract changed symbols via git diff
  • find callers using grep
  • mark source as grep-fallback in impact map

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.