workflow-preflight
Pre-work validation before implementation. Use when starting an issue or fix to verify remote state, check for existing PRs, and detect branch conflicts before coding.
What this skill does
# /workflow:preflight Pre-work validation to prevent wasted effort from stale state, redundant work, or branch conflicts. ## When to Use This Skill | Use this skill when... | Skip when... | |------------------------|-------------| | Starting work on a new issue or feature | Quick single-file edit | | Resuming work after a break | Already verified state this session | | Before spawning parallel agents | Working in an isolated worktree | | Before creating a branch for a PR | Branch already created and verified | ## Context - Repo: !`git remote get-url origin` - Current branch: !`git branch --show-current` - Remote tracking: !`git branch -vv --format='%(refname:short) %(upstream:short) %(upstream:track)'` - Uncommitted changes: !`git status --porcelain` - Stash count: !`git stash list` ## Execution ### Step 1: Fetch Latest Remote State ```bash git fetch origin --prune 2>/dev/null ``` ### Step 2: Check for Existing Work If an issue number was provided, check if it's already addressed: ```bash # Check if issue exists and its state gh issue view $ISSUE --json number,title,state,labels 2>/dev/null # Check for PRs that reference this issue gh pr list --search "fixes #$ISSUE OR closes #$ISSUE OR resolves #$ISSUE" --json number,title,state,headRefName 2>/dev/null # Check for branches that reference this issue git branch -a --list "*issue-$ISSUE*" --list "*fix/$ISSUE*" --list "*feat/$ISSUE*" 2>/dev/null ``` **If a merged PR exists**: Report that the issue is already addressed. Stop. **If an open PR exists**: Report the PR and ask if the user wants to continue on that branch or start fresh. ### Step 3: Verify Branch State ```bash # Check divergence from main/master git log --oneline origin/main..HEAD 2>/dev/null || git log --oneline origin/master..HEAD 2>/dev/null # Check if main has moved ahead git log --oneline HEAD..origin/main -5 2>/dev/null || git log --oneline HEAD..origin/master -5 2>/dev/null # Check for uncommitted changes git status --porcelain=v2 --branch 2>/dev/null ``` **Report**: - Commits ahead/behind remote - Uncommitted changes that might interfere - Whether a rebase is needed ### Step 4: Check for Conflicts ```bash # Dry-run merge to detect conflicts (without actually merging) git merge-tree $(git merge-base HEAD origin/main) HEAD origin/main 2>/dev/null | head -20 ``` ### Step 5: Summary Report Output a structured summary: | Check | Status | Detail | |-------|--------|--------| | Remote state | fresh/stale | Last fetch time | | Existing PRs | none/open/merged | PR numbers if any | | Branch state | clean/dirty/diverged | Ahead/behind counts | | Conflicts | none/detected | Conflicting files | | Stash | empty/N items | Stash contents | **Recommendations**: - If behind remote: "Rebase recommended before starting work" - If existing PR found: "PR #N already addresses this - review before duplicating" - If dirty state: "Commit or stash changes before branching" - If conflicts detected: "Resolve conflicts with main before proceeding" - If clean: "Ready to proceed" ## Agentic Optimizations | Context | Command | |---------|---------| | Quick remote sync | `git fetch origin --prune 2>/dev/null` | | Check existing PRs | `gh pr list --search "fixes #N" --json number,state,headRefName` | | Branch divergence | `git log --oneline origin/main..HEAD` | | Conflict detection | `git merge-tree $(git merge-base HEAD origin/main) HEAD origin/main` | | Compact status | `git status --porcelain=v2 --branch` | | Remote tracking | `git branch -vv --format='%(refname:short) %(upstream:track)'` | ## Quick Reference | Flag | Description | |------|-------------| | `git fetch --prune` | Fetch and remove stale remote refs | | `git status --porcelain=v2` | Machine-parseable status | | `gh pr list --search` | Search PRs by content | | `gh issue view --json` | Structured issue data | | `git merge-tree` | Dry-run merge conflict detection | | `git log A..B` | Commits in B but not A |
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.