chore
Generate a comprehensive chore plan from a one-line description. Use for maintenance tasks, cleanup, refactoring, or dependency updates.
What this skill does
# Chore Planning Create a new plan in `specs/*.md` to resolve the Chore using the exact specified markdown Plan Format. Follow the Instructions to create the plan, use the Relevant Files to focus on the right files. ## Instructions - You are writing a plan to resolve a chore, NOT implementing it yet - Use your reasoning model: THINK HARD about the plan and the steps to accomplish the chore - Read the codebase to understand current patterns and structure - Focus on the files in the Relevant Files section when identifying what to modify - Fill in EVERY section of the Plan Format - no empty sections - Include realistic validation commands that actually verify completion - Keep the plan focused - don't expand scope beyond the chore description ## Relevant Files Focus on the following files to understand the codebase: - README.md (project structure and conventions) - CLAUDE.md (agent instructions if present) - src/**or app/** (source code patterns) - scripts/** (existing automation) - tests/** (test patterns to follow) ## Plan Format Write the plan to `specs/chore-<descriptive-name>.md` using this exact format: ```markdown # Chore: <descriptive-name> ## Chore Description <Clear explanation of what needs to be done and why this is valuable> ## Relevant Files <List all files that will be created, modified, or deleted> ## Step by Step Tasks 1. <First specific, actionable task> 2. <Second specific task with file references> 3. <Continue with numbered tasks> ## Validation Commands <Commands that prove the work is complete> - Run `<command>` to verify <what> - Run `<command>` to verify <what> ## Notes <Edge cases, dependencies, gotchas, or related work to consider> ``` ## Chore $ARGUMENTS
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.