Repo Modernize Upgrade Audit
Use this skill when you need to audit, upgrade, refactor, and simplify a repo
or monorepo end-to-end around dependencies, security findings, deprecations,
and framework migrations.
Variant References
Use the base prompt below by default. If the repo shape or workflow calls for a
specialized operating mode, load the matching reference first:
references/00-variant-index.mdreferences/framework-lane-selection.mdreferences/dependency-decision-matrix.mdreferences/verification-matrix.mdreferences/report-template.mdreferences/bun-first.mdreferences/pnpm-turbo-monorepo.mdreferences/plan-first.md
Selection guidance:
- Bun-managed repos: start with
references/bun-first.md
- pnpm + Turbo monorepos: start with
references/pnpm-turbo-monorepo.md
- review-heavy or approval-gated work: start with
references/plan-first.md
- framework-heavy repos: also read
references/framework-lane-selection.md
- during package triage: read
references/dependency-decision-matrix.md
- before execution wrap-up: read
references/verification-matrix.md
- for final delivery: read
references/report-template.md
- if unclear: read
references/00-variant-index.md first
Intent
- Find every vulnerable dependency, outdated dependency, deprecated API,
obsolete custom abstraction, and dependency-driven cleanup opportunity.
- Deeply research the latest official docs, changelogs, migration guides,
release notes, GitHub releases, advisories, and upstream issues.
- Upgrade dependencies to the latest safe and supportable versions.
- Refactor the codebase to adopt modern dependency-native APIs and delete
obsolete wrappers, shims, fallbacks, and duplicate implementations.
- Leave the repo in a verified, production-ready, simplified state.
Required Skills and Tools
Use these throughout the task:
$bun-dev$hard-cut$clean-code$reducing-entropy$githubcontext7web.run
Use $opensrc conditionally as an escalation path for package upgrades
that need source-level proof.
Framework-specific routing is defined in the execution prompt below and refined
further in references/framework-lane-selection.md.
Execution Prompt
For full execution mode, load references/execution-prompt.md. It contains the complete modernization prompt, research requirements, dependency audit workflow, framework lanes, upgrade strategy, verification expectations, and final report contract.
Keep this entrypoint focused on routing and reference selection. Do not duplicate framework-specific playbooks here; use the variant references above.
1---2name: repo-modernize-upgrade-audit3description: Repo/monorepo—dep modernize, vuln fix, framework-aware upgrade, hard-cut, dep-native refactors.4---5
6# Repo Modernize Upgrade Audit
7
8Use this skill when you need to audit, upgrade, refactor, and simplify a repo
9or monorepo end-to-end around dependencies, security findings, deprecations,
10and framework migrations.
11
12## Variant References
13
14Use the base prompt below by default. If the repo shape or workflow calls for a
15specialized operating mode, load the matching reference first:
16
17- `references/00-variant-index.md`
18- `references/framework-lane-selection.md`
19- `references/dependency-decision-matrix.md`
20- `references/verification-matrix.md`
21- `references/report-template.md`
22- `references/bun-first.md`
23- `references/pnpm-turbo-monorepo.md`
24- `references/plan-first.md`
25
26Selection guidance:
27
28- Bun-managed repos: start with `references/bun-first.md`
29- pnpm + Turbo monorepos: start with `references/pnpm-turbo-monorepo.md`
30- review-heavy or approval-gated work: start with `references/plan-first.md`
31- framework-heavy repos: also read `references/framework-lane-selection.md`
32- during package triage: read `references/dependency-decision-matrix.md`
33- before execution wrap-up: read `references/verification-matrix.md`
34- for final delivery: read `references/report-template.md`
35- if unclear: read `references/00-variant-index.md` first
36
37## Intent
38
39- Find every vulnerable dependency, outdated dependency, deprecated API,
40 obsolete custom abstraction, and dependency-driven cleanup opportunity.
41- Deeply research the latest official docs, changelogs, migration guides,
42 release notes, GitHub releases, advisories, and upstream issues.
43- Upgrade dependencies to the latest safe and supportable versions.
44- Refactor the codebase to adopt modern dependency-native APIs and delete
45 obsolete wrappers, shims, fallbacks, and duplicate implementations.
46- Leave the repo in a verified, production-ready, simplified state.
47
48## Required Skills and Tools
49
50Use these throughout the task:
51
52- `$bun-dev`
53- `$hard-cut`
54- `$clean-code`
55- `$reducing-entropy`
56- `$github`
57- `context7`
58- `web.run`
59
60Use `$opensrc` conditionally as an escalation path for package upgrades
61that need source-level proof.
62
63Framework-specific routing is defined in the execution prompt below and refined
64further in `references/framework-lane-selection.md`.
65
66## Execution Prompt
67
68For full execution mode, load [references/execution-prompt.md](references/execution-prompt.md). It contains the complete modernization prompt, research requirements, dependency audit workflow, framework lanes, upgrade strategy, verification expectations, and final report contract.
69
70Keep this entrypoint focused on routing and reference selection. Do not duplicate framework-specific playbooks here; use the variant references above.
aibot88