agentsclimarketplace
Sign in

Managed codebase context

Skill yeaight7/agent-powerups/plugins/codebase-intelligence/skills/managed-codebase-context

Use when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context.From its SKILL.md

Install
npx -y skills add yeaight7/agent-powerups --skill managed-codebase-context

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

  • 6 stars6 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

2.9 KB, 572 tokens by cl100k_base, as published. Nobody here has run it

Managed Codebase Context

When to use

Use when a persistent codebase-context MCP server is available and the task requires broad architectural context, symbol inventory, or cross-file navigation that would be expensive to reconstruct from scratch on each turn.

Requirements / Checks

  • Check MCP transport type: stdio (local, one-off) vs HTTP (requires a running server).
  • Do not run npx -y or start server processes without user approval.
  • Verify server cwd, env variables, timeout, and workspace path scope.
  • Confirm cleanup behavior for spawned stdio processes before starting long-running tasks.

Workflow

  1. Select transport:

    • stdio: suitable for local, ephemeral sessions started per task.
    • HTTP: use only when a local server is already confirmed to be running.

  2. Connect with timeout — set a connection timeout; do not let the agent hang indefinitely if the server never initializes.

  3. Retrieve context — fetch the current codebase map, symbol index, or architectural summary as available.

  4. Validate freshness — a map is stale if any of the following are true:

    • Map timestamp predates the last git commit that touched relevant files.
    • Map references files that no longer exist.
    • Map is missing files present in the current workspace.
    • The user reports recent significant refactoring.

  5. Refresh when stale — trigger a context refresh only when the map is demonstrably stale. Do not refresh on every request — refreshes are expensive.

  6. Use context, then close — read what you need, then close the session. Ensure the client and transport close cleanly. If the server was spawned as a stdio process, kill the process tree if it does not exit within a few seconds.

Staleness Signals

SignalCheck
Map timestampCompare to git log --format="%ci" -1 for recently changed files
Missing filesCross-reference map file list with git ls-files
Stale symbolsCheck if key function/class names in the map exist in current source
User-reportedAccept the user's word; trigger refresh without verification

Safety Constraints

  • Only interact with paths scoped to the current workspace.
  • Do not overwrite existing architectural documents without user confirmation.
  • Do not import user-level or global MCP configs implicitly.
  • Do not leave background server processes running after a failed connection.

Validation / Done Criteria

  • Context retrieved is confirmed to be within the current workspace scope.
  • Freshness was validated or a refresh was triggered with reason.
  • Any spawned MCP process is closed or explicitly left running by user choice.

References

  • references/managed-session-checklist.md

What ships with it: 1 file

1.2 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most architecture codebase skills give in 572 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

  • check MCP transport type before connecting
  • verify server scope before starting
  • confirm cleanup behavior for spawned processes
  • retrieve the codebase map or symbol index
  • validate map freshness against recent git history
  • refresh context only when demonstrably stale

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,835. 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.