resolve-issues
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
What this skill does
# Resolve GitHub Issues Execute issue resolution workflow using isolated worktrees, TDD methodology, and agent collaboration. ## Context - Current git status: !`git status` - Current branch: !`git branch --show-current` - Existing worktrees: !`git worktree list` - Open issues: !`gh issue list --state open --limit 10` - GitHub authentication: !`gh auth status` ## Requirements Summary Use isolated worktrees to avoid disrupting main development. Follow TDD cycle (red → green → refactor) with agent support. Reference issues in commits using auto-closing keywords. See `references/requirements.md` for protected PR workflow and commit standards. ## Phase 1: Issue Selection and Worktree Setup **Goal**: Select target issue and prepare isolated development environment. **Actions**: 1. Review open issues from context and select based on priority and `$ARGUMENTS` 2. Check existing worktrees to determine if reuse is possible 3. Use the EnterWorktree tool with a descriptive name (e.g., `fix-456-auth-redirect`) to create an isolated session 4. Rename the auto-generated branch to match conventions: run `git branch -m <type>/<issue>-<description>` (see `references/workflow-details.md` for naming) 5. Verify issue acceptance criteria and dependencies ## Phase 2: TDD Implementation **Goal**: Implement fix using test-driven development with agent collaboration. **Actions**: 1. Plan implementation approach and assess architectural impact 2. Write failing tests that verify issue is resolved (RED phase) 3. Implement minimal code to make tests pass (GREEN phase) 4. Refactor while keeping tests green (REFACTOR phase) 5. Run quality validation commands (see `references/workflow-details.md` for project-specific checks) ## Phase 3: PR Creation and Cleanup **Goal**: Create pull request, link issue, and clean up worktree after merge. **Actions**: 1. Push branch to remote with `git push -u origin <branch-name>` 2. Create PR using `gh pr create` with auto-closing keywords (e.g., "Closes #456") if targeting the default branch. If targeting a non-default branch, warn the user they will need to close the issue manually. - Consider using `--draft` if the fix requires further feedback before review 3. Report PR URL and status to user 4. After successful merge: use the ExitWorktree tool with action "remove" to clean up worktree and branch 5. Document resolution and any follow-up tasks ## References - **Requirements**: `references/requirements.md` - Worktree setup, TDD, and commit standards - **Workflow Details**: `references/workflow-details.md` - Issue selection, TDD cycle, agent collaboration - **Examples**: `references/examples.md` - Commit message examples
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.