agentsclimarketplace

Context retrieval loop

Skill yeaight7/agent-powerups/plugins/codebase-maintenance/skills/context-retrieval-loop

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

Install
npx -y skills add yeaight7/agent-powerups --skill context-retrieval-loop

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.

What its author says it does

Copied from the file, not written here

Use when about to refactor, rename, or remove code, assessing dead code before deletion, or unsure of the blast radius of a change.

SKILL.md

1.8 KB, as published. Nobody here has run it

Context Retrieval Loop (Codebase Maintenance)

Gather context before any refactor or maintenance task. Prevents breaking undetected callers or missing test coverage.

When to Use

  • About to refactor, rename, or remove code
  • Assessing dead code before deletion
  • Unsure of the blast radius of a change

The 3-Cycle Loop

Cycle 1 — Broad Search

# Find callers and references
rg "<symbol-name>" --type ts --type js -l
rg "<symbol-name>" --glob "*.py" -l

Stop here if you can confirm the symbol is unused (no results).

Cycle 2 — Exact Source and Tests

Read the target file and its tests. Find all callers:

rg "import.*<module>" -l
rg "<function-name>" --glob "*.test.*" -l

Stop here if you understand the change scope and existing test coverage.

Cycle 3 — Config and Build

# Check if symbol appears in build or config
rg "<symbol-name>" *.config.* tsconfig.json Makefile -l 2>/dev/null

Check for re-exports, barrel files, and public API surfaces.

Output

Context gathered:
  <file-path> — <reason>

Blast radius:
  <N> callers in <N> files
  Tests covering this code: <yes/no/partial>

Missing context (if any):
  <what is still unclear>

Do not start a refactor without knowing the blast radius. If callers are unclear after Cycle 3, stop and report.

Verification

  • Cycles ran in order and stopped at the first satisfied condition — never past 3
  • Blast radius is reported: caller count, files affected, test coverage status
  • Re-exports, barrel files, and public API surfaces were checked before concluding
  • No refactor started while callers remained unclear — stopped and reported instead

Keep looking

Skills are one crate of 328,083. 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.