agentsclimarketplace
Sign in

Repo map refresh

Skill MostAshraf/ai-sdlc-harness/skills/repo-map-refresh

Regenerate the auto-generated repo map the planner grounds its plans in. USER-ENTRY — invoke only when the user explicitly runs /repo-map-refresh; never autonomously, never from a subagent (guard-enforced).From its SKILL.md

Install
npx -y skills add MostAshraf/ai-sdlc-harness --skill repo-map-refresh

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

  • 15 stars15 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.4 KB, as published. Nobody here has run it

repo-map-refresh

The repo map is a navigation aid, never hand-maintained — corrections go through regeneration (design.md piece 5B). /init-workspace and /add-repo both point here for the identical generate-or-regenerate procedure (step 2 below) — this is the one place it's maintained; don't fork a second copy of it elsewhere.

  1. ${CLAUDE_PLUGIN_ROOT}/bin/harness repo-map-check --repo-name <n> --repo <path> — report missing / fresh / stale (+ commits behind) to the user.
  2. To regenerate: spawn the planner shape with harness-mode: repo-map as the prompt's FIRST line (the spawn guard regex-matches this exact header — prose that merely mentions repo-map does not satisfy it; this is a declared out-of-run spawn, pipeline/surfaces.yaml's out_of_run_spawns, legal regardless of whether other runs exist in the workspace) and the repo path. Pass run_in_background: false where the Agent tool has that parameter (under Qwen Code the guard requires it); where it does not, the spawn returns a launch stub and runs in the background — wait for its completion notification before step 3. For the correct subagent_type and why a wrong identity is now blocked, see shared/spawn-identity.md — match the frontmatter name: ai-sdlc-planner, never a generic agent. The planner can only write under ai/<run>/ and .claude/context/ (guard-enforced — never repo source), so point it at .claude/context/repo-map/<name>/. It follows the map content contract (${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/steps/repo-map-task.md): index.md (purpose/stack/modules/cross-repo edges — intake's targeting tier), areas/* detail files (each loadable alone), and conventions.md (observed patterns with cited examples — what plan-review checks plans against).
  3. Stamp it yourself, not the planner: ${CLAUDE_PLUGIN_ROOT}/bin/harness repo-map-stamp --repo-name <n> --repo <path> — stamping is the orchestrator's job, never the planner's own.
  4. Remind the user: the planner still reads real code for areas it plans to touch — the map speeds targeting, it doesn't replace reading.

Keep looking

Skills are one crate of 627,801. 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.