gh-inbox
Collect and triage a GitHub work inbox from assigned issues, review requests, mentions, authored PRs with failing checks, and optional project filters. Use when checking what needs attention across GitHub or prioritizing GitHub tasks.
What this skill does
# GH Inbox Turn scattered GitHub work into a small priority queue. ## Contract Inputs: - Optional repository, owner, or project filter - Optional limit and priority rules Outputs: - Prioritized GitHub inbox summary - Recommended next actions - Commands for follow-up inspection Creates/Modifies: - None in report mode - May label, comment, assign, close, or move items only after approval External Side Effects: - Reads GitHub issues, PRs, reviews, checks, and project membership - Writes GitHub issue/PR/project state only after approval Confirmation Required: - Before editing labels, assignees, comments, project fields, or issue state - Before rerunning workflows - Before merging or closing anything Delegates To: - `gh-fix-ci` for failing PR checks - `gh-address-comments` for existing review comments - `gh-review-suggestions` when a PR needs inline review feedback - `gh-project-board` when board metadata is missing or inconsistent ## Workflow 1. Verify auth: ```bash gh auth status -h github.com gh api user --jq .login ``` 2. Generate the inbox: ```bash node skills/gh-inbox/scripts/gh-inbox-report.mjs ``` Common filters: ```bash node skills/gh-inbox/scripts/gh-inbox-report.mjs --owner shipshitdev node skills/gh-inbox/scripts/gh-inbox-report.mjs --repo shipshitdev/shipcode node skills/gh-inbox/scripts/gh-inbox-report.mjs --project shipshitdev/1 node skills/gh-inbox/scripts/gh-inbox-report.mjs --limit 50 ``` 3. Triage order: - Review requests - Authored PRs with failing checks - Assigned P0/P1 or blocking issues - Mentions needing a response - Stale assigned issues - Project-board items missing status or priority 4. For each item, choose one next action: - Inspect - Fix - Reply - Defer - Reassign - Close 5. Ask before applying any writes. When writing, use the smallest command: ```bash gh issue edit <number> --add-label "priority:P1" gh issue comment <number> --body-file <file> gh pr review <number> --comment --body-file <file> ``` ## Rules - Prefer a short queue over a complete dump. - Keep review requests above authored work unless production is blocked. - Treat failing checks as actionable only after reading the failure. - Do not close or defer user-facing issues without leaving a reason. - If GitHub search results are noisy, narrow by `--repo`, `--owner`, or `--project` before making recommendations.
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.