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.
What this skill does
# Codebase Singularity ## Quick start 1. Collect inputs: repo path, goal, constraints, risk tolerance, and validation commands. 2. Prime: list files, read README, and inspect entry points. 3. Summarize: explain repo shape and where the change belongs; ask questions if ambiguous. 4. Plan: write a short plan with success criteria and validation steps. 5. Change: implement the smallest viable patch; avoid unrelated refactors. 6. Validate: run the requested command(s) or the closest available; record results. 7. 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. ## Grades (maturity ladder) ### Grade 1: Prime only - Prime, summarize, and stop on ambiguity. ### Grade 2: Specialized roles + verification - Add role prompts (e.g., test_writer, docs_fetcher, reviewer). - Require a verification step for each role. ### Grade 3: Tooling expansion - Declare required tools or services and expected outputs. - Prefer tools over guessing (e.g., query schema instead of inferring). ### Grade 4: Closed-loop autonomy - Run cycles: request -> validate -> resolve. - Add hard exits: max iterations, evidence of progress, stop after repeated failures. ## Guardrails - Keep diffs small. - 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.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.