codebase-recon
FeaturedReconstruct a repository as cited entry-to-test flows and bounded claims. Triggers: "codebase recon", "trace this codebase", "repository audit", "refresh the prior recon".
Install
Quality Score: 96/100
Skill Content
Details
- Author
- boshu2
- Repository
- boshu2/agentops
- Created
- 8 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
repo-recon
Systematically map an unfamiliar codebase before changing anything in it. Use this whenever work starts in a repo, service, or module that has not been explored in the current session, when the user says things like "new codebase", "help me understand this project", "onboard me", or before any non-trivial change where the surrounding code is unknown. Also reach for it after a change failed because of a wrong assumption about project structure or conventions.
kookr-oss-repo-recon
Analyze an open-source repository's contribution requirements — CONTRIBUTING.md, PR template, CI config, CLA, build system, key reviewers — before attempting any contribution
codebase-rescue
Rescue and elevate a whole codebase — especially large AI-generated / "vibecoded" ones — by reconciling backend, frontend, and database into an aligned, state-of-the-art state. Use this whenever the user wants to audit, rescue, resume, clean up, or "save" a codebase; whenever they mention slop code, a messy/abandoned/half-finished project, layers that are not aligned or contradict each other, or turning a prototype into something production-grade. Trigger even when the user only says things like "review my whole app", "the frontend and backend don't match", "pick up where I left off", "this codebase is a mess", or "make this production-ready" — do not wait for the word "audit". Prefer this skill over ad-hoc file reading or generic security review for anything that spans multiple layers or the codebase as a whole.