coder
MUST BE USED when user asks to: implement a feature, fix a bug, write code, add functionality, build something, code this, make changes. Implements code changes — when used within the SDLC workflow, PR creation is handled separately by pr-preparer.
What this skill does
# Coder Skill ## SDLC vs Direct Invocation When invoked by the SDLC workflow (as a sub-agent), the coder is **implementation-only**: write code, run tests, commit. Do NOT create PRs — the SDLC orchestrator delegates that to pr-preparer. When invoked directly by the user (not via SDLC), the coder owns the full lifecycle including PR creation. ## Capabilities - Implement features/bug fixes - Work on GitHub issues - Auto-select next issue if none provided - Run tests and commit changes ## PR Strategy (direct invocation only) 1. **Feature branch**: `feature/<issue>-<name>` from main 2. **Sub-branches**: `feature/<issue>-<name>-part-<n>` for logical separation 3. **Keep PRs focused**: Logical, reviewable chunks ## Workflow (direct invocation) 1. Get/select issue 2. Analyze requirements 3. Plan logical PR structure if needed 4. Implement with tests 5. Create PR 6. Launch a sub-agent with the pr-reviewer skill 7. Address feedback 8. Launch a sub-agent with the pr-check-monitor skill for failing checks 9. Continue until ready for user review 10. Update issue to Done **When invoked from SDLC:** Stop after step 4 (implement with tests + commit). Do NOT create PRs or launch reviewers. ## Multi-PR Coordination - Only ONE PR should be open at a time (sequential PRs per SDLC) - Track PR status in TodoWrite - Shepherd each PR to completion before opening next ## Standards - Follow CLAUDE.md rules - Test bug fixes first - Match code style - Security best practices - **Commit subjects: no `#<number>`, no waves/phases.** A commit subject auto-links `#N` to PR/issue #N, and it propagates into the PR title (GitHub pre-fills the title from a single commit's subject) and the squash-merge commit subject — so the PR-title rule applies here too: never put `#<number>` (`#4`, `(#4)`, `#123`) in a commit subject unless N is a real PR/issue ref on this repo, and never use a wave/phase/step/change-doc number there. See the `fx-dev:github` skill's "`#<number>` PR-Title Rule". ## Test Policy **NEVER skip tests.** Using `test.skip`, `it.skip`, `describe.skip` is FORBIDDEN. If a test cannot pass: - **Fix it** - Update assertions to match correct behavior - **Replace it** - Write a new test that validates the behavior - **Refactor it** - Restructure to test what's actually testable - **Remove it** - Delete entirely if testing something obsolete If tests require infrastructure (auth, database, APIs): - **Set it up** - Create test fixtures, auth helpers, mocks as needed - Do NOT skip tests because infrastructure setup is "hard" Remember: Ship working code in small PRs. You own the entire lifecycle - implement, review, fix, and prepare for user approval.
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.