fix-github-issue
Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.
What this skill does
# GitHub Issue Fixer Fix GitHub issues by implementing solutions on feature branches with proper testing. ## Prerequisites - `gh` CLI installed and authenticated - Repository cloned locally - Test command available (auto-detected or specified) ## Workflow ### 1. Understand the Issue ```bash gh issue view <issue-number> ``` Read the issue thoroughly. ### 2. Create Feature Branch ```bash git checkout main && git pull origin main git checkout -b fix-<short-description> ``` Branch naming: `fix-description` (lowercase, hyphens). ### 3. Analyze the Codebase Before coding, understand the relevant parts: - Locate files related to the issue - Check existing tests for patterns - Review any referenced code in the issue ### 4. Implement the Fix Make minimal, focused changes that address the issue. Follow existing code style and patterns. ### 5. Run Tests Locally Detect and run the test suite. Most likely it will be pest or phpunit. Take a look what is defined in composer.json or the testing github file. **Tests must pass locally before proceeding.** If tests fail: 1. Analyze failures 2. Fix the implementation 3. Re-run until all pass ### 6. Commit Changes ```bash git add -A git commit -m "Fix #<issue-number>: <concise description>" ``` Use conventional commit message referencing the issue number. ### 7. Push and Create PR ```bash git push -u origin fix/issue-<issue-number>-<short-description> gh pr create --title "Fix #<issue-number>: <title>" --body "Fixes #<issue-number> ## Changes - <bullet points of changes> ## Testing - All local tests pass - <any additional testing done>" ``` ### 8. Monitor CI ```bash gh pr checks --watch ``` If CI fails: 1. Review the failure: `gh run view <run-id> --log-failed` 2. Fix locally 3. Push additional commits 4. Repeat until CI passes ## Quick Reference ```bash # View issue gh issue view 123 # Create branch git checkout -b fix/issue-123-description # After fixing and tests pass git add -A && git commit -m "Fix #123: description" git push -u origin fix/issue-123-description gh pr create --fill # Watch CI gh pr checks --watch ```
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.