codebase-singularity
/codebase-singularity
Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.
- Author
- vishalsachdev ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 03.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.
Original author description
Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.
How it works
- Quick start
- Inputs
- Outputs
- Guardrails
- Templates
- References
SKILL.md preview
--- name: codebase-singularity description: "Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria." --- # Codebase Singularity ## Quick start 1. Collect inputs: repo path, goal, constraints, risk tolerance, and validation commands. 2. Summarize: explain repo shape and where the change belongs; ask questions if ambiguous. 3. Plan: write a short plan with success criteria and validation steps. 4. Change: implement the smallest viable patch; avoid unrelated refactors. 5. Validate: run the requested command(s) or the closest available; record results. 6. Wrap up: report changes, evidence, risks, and next steps. ## Inputs - Repo path and task goal. - Constraints (files to avoid, time or risk limits, API stability). - Validation commands (tests, lint, build, or targeted checks). ## Outputs - Short plan with success criteria. - Minimal patch. - Evidence: commands run and results. - Wrap-up: what changed, why, risks, and next steps. ## Guardrails - Always validate; if you cannot, say so and propose a safe next step. - Ask before broad refactors or scope expansion. ## Templates ### Safe bugfix ``` Goal: Fix <bug> with minimal change. Constraints: Do not modify public API; avoid touching <paths>. Validation: Run `...` and paste output. Exit conditions: Stop after 2 failed attempts; summarize hypotheses and logs. Deliverables: Patch + explanation + risks. ``` ### Add a feature ``` Goal: Add <feature>. Constraints: Keep scope to <module>; no new dependencies. Validation: Run `...`. Deliverables: Patch + tests + short doc update. ``` ## References - Read `references/video.md` for a concise source summary. - Read `references/transcript.md` for full context. - Read `references/visual-notes.md` for a visual outline. - Read `references/maturity-ladder.md` for the grades/maturity taxonomy.
Files in this package (6)
- SKILL.md 2 KB
- references/maturity-ladder.md 1 KB
- references/transcript.md 42 KB
- references/video.md 1 KB
- references/visual-notes.md 9 KB
- references/visual-selection.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vishalsachdev/claude-skills | 100 | MIT |
| vishalsachdev/claude-code-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version e1c81d006f83 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100focused-fix
This skill should be used when the user asks to "fix a bug with minimal changes", "analyze change scope for a bugfix", "find the minimal set of files to change", "do a focused bugfix", or "scope a minimal repair". - 90kata
Implement software through small, repeatable, integrated vertical slices with clear exit criteria and honest verification. Use when a design is understood and code needs to be built or changed. - 90refactor
Plan, implement, or review refactor work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests refactor work. - 100singularity-apptainer
Use when the user asks about Singularity, Apptainer, HPC containers, running containers on clusters, or converting Docker images for HPC environments. Creates definition files, builds and validates .sif images, configures MPI/GPU execution, and integrates container runs with Slurm. - 100codebase-onboarding
Maps an unfamiliar repository before changing it - stack, build/test/run commands, entry points, data flow, conventions and how changes ship - and writes a short map. Use when starting work in a repo you have not seen, when asked to explain how a codebase works, onboard to a…