Menú
Use on first Fusebase Flow install, opening an unfamiliar repo, or after major restructuring; produces durable context map (commands, structure, protected paths, risky boundaries). Do NOT use for routine ticket investigation.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use ONLY when the operator runs "/find-wasted-code" (or explicitly asks to "scan the repo for dead-end tool calls / broken links / missing helpers / footgun configs / silent push-through"). Statically scans THIS repo for friction footguns and writes a tracked report to docs/wasted-code/report.md. Manual-trigger ONLY — do NOT auto-invoke; the skill carries disable-model-invocation and no hook wires it. Read-only except the one report write. Findings are review candidates, never auto-fixes. Do NOT use for token/transcript economy (/token-waste-audit), for process ceremony (/find-wasted-effort), or for CLI/Flow drift health (/fusebase-health).
Use at Specify to classify a ticket Full vs Lightweight, and whenever a change looks small / reversible / low-risk ("small fix", "tweak", "hotfix", "drop pretty-printing", "bump a constant"). Operationalizes FR-21 — ceremony proportional to change size. Defines the eligibility gate, the change-note artifact, the one-pass build→verify→deploy procedure, and mid-flight promotion. Do NOT use for risky/uncertain work, schema/data migrations, security/permission changes, new public contracts needing a decision, unknown-root-cause diagnostics, or large features — those take the Full lane.
ALWAYS load at session start. After self-attesting, Read references/<role>.md for your role (Product Owner / AI Developer / Architect / Deploy phase) — role-specific don't-list, exact refusal phrasing for FR violations, and recovery pointers; shared cross-role protocols live in this file. Mandatory; not on-demand.
Use when the operator types /product-owner, asks to activate Product Owner, start a Product Owner or PO session, or searches /product in Codex for Fusebase Flow project management. Do NOT use for implementing code; route implementation to the AI Developer role.
Use when planning tasks that touch big source files, when an edit would push a file past the module-size ceiling, when the pre-commit module-size ratchet warns or blocks, or when generating policies/module-size-baseline.txt. Operationalizes FR-25 — module-size ratchet (ceiling default 800; over-ceiling files may shrink, never grow; extraction along a responsibility seam is in-scope, not scope creep). Do NOT use for docs/markdown size (FR-23 owns docs), to force decomposition of an existing monolith (that is its own explicit ticket), or to judge split quality by regex (seam-vs-mechanical is semantic — code-review owns it).
Use ONLY when verification passed AND operator explicitly says "prepare deploy" / "draft deploy" / "ship it"; drafts deploy handoff, captures deploy hash + probes + smoke, advises spec DRAFT→DONE flip. Do NOT auto-invoke; operator triggers explicitly.
| name | repo-onboarding-context-map |
| description | Use on first Fusebase Flow install, opening an unfamiliar repo, or after major restructuring; produces durable context map (commands, structure, protected paths, risky boundaries). Do NOT use for routine ticket investigation. |
| source_inspiration | conceptual-only |
| license_status | clean-room-original |
| fusebase_flow_version | 3.30.8 |
| risk_level | low |
| invocation | manual |
| expected_outputs | ["docs/specs/repo-context.md","AGENTS.md (project-specific section, recommended updates)"] |
| related_workflows | ["setup.md","session-initiation.md"] |
| hook_dependencies | ["none"] |
Inspect an unfamiliar repo and produce a durable context map so future sessions know the project's structure, commands, protected paths, and risky system boundaries without re-investigating each session.
Named reader: workflows/session-initiation.md step 5 — every new session reads docs/specs/repo-context.md when it exists and is <90 days old, instead of re-investigating. The map header MUST carry Generated: <YYYY-MM-DD> so readers can apply the freshness gate.
docs/specs/repo-context.md is missing or older than 90 daysrepo-context.md exists and the repo hasn't changed structurally| Input | Where it lives | If missing |
|---|---|---|
| Repo root | git root | Stop; ask operator to confirm working directory |
| Package/project files | package.json, pyproject.toml, Cargo.toml, etc. | Note "no manifest detected"; describe based on file extensions only |
| Existing READMEs | README.md, docs/, etc. | Note absence; flag as Phase-4 onboarding gap |
| CLI edition map, for this edition | docs/fusebase-cli-edition.md | Continue with generic repo map, but mark CLI provider asset mapping unknown |
README.md if present. Read up to 3 most-referenced docs in docs/.docs/fusebase-cli-edition.md and record which CLI provider assets are present and relevant.git log --oneline -30 to read commit cadence + recent areas of activity.docs/specs/repo-context.md using templates/spec.md adapted for context-mapping (see template). Stamp a Generated: <YYYY-MM-DD> line in the header — workflows/session-initiation.md step 5 uses it for the 90-day freshness gate.AGENTS.md "project-specific values" section. Show the diff in chat. Do NOT apply unless operator says "apply".policies/protected-paths.yml candidates. Save as draft if operator approves; do NOT auto-write.| Artifact | Path | Mode |
|---|---|---|
| Repo context map | docs/specs/repo-context.md | Mode B (full) |
| AGENTS.md project-specific updates (proposed) | chat diff | Mode A |
| Protected paths candidates | policies/protected-paths.yml (proposed; commit only on operator approval) | Mode B (full, YAML) |
| Failure mode | Detection | Response |
|---|---|---|
| Repo has no manifest, no README, no docs | Initial scan returns nothing identifying | Capture what's visible (file extensions, recent commits). Mark repo-context.md as partial and ask operator to fill the gaps. |
| Repo is a monorepo with conflicting conventions | Multiple package.json / pyproject.toml at different paths | Map each subdir separately. Flag in repo-context.md "monorepo: yes". |
| Repo uses git submodules | .gitmodules exists | Note submodules in repo-context.md but do not recurse into them; map a submodule only if the operator explicitly asks. |
AGENTS.md updates — propose, get operator approval, then writepolicies/protected-paths.yml candidates without operator approvalOriginal Fusebase Flow content. Designed after reviewing public AI coding workflow patterns; no third-party code, prompts, skill files, or hook scripts are copied. See docs/source-map.md.