codebase-singularity
Codebase Singularity
Quick start
- Collect inputs: repo path, goal, constraints, risk tolerance, and validation commands.
- Prime: list files, read README, and inspect entry points.
- Summarize: explain repo shape and where the change belongs; ask questions if ambiguous.
- Plan: write a short plan with success criteria and validation steps.
- Change: implement the smallest viable patch; avoid unrelated refactors.
- Validate: run the requested command(s) or the closest available; record results.
- 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).
More from vishalsachdev/claude-code-skills
paper-writing
Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.
744formbuilder-admin
>
5tweet-series-extractor
|
1start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
1agentic-validators
Design and install validation hooks for coding agents (e.g., Claude Code) to make AI changes safer and more deterministic. Use when you want post-tool-use or stop hooks, automated tests/linters/formatters, parallel subagents with per-file validation, or a repeatable “agent pipeline” with audit logs.
1wrap-up-session
Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.
1