yeet
Use when the user says "yeet" or "/yeet" to quickly stage, review, commit, and push all changes with a provided message
What this skill does
# Yeet Fast commit-and-push. Usage: `/yeet "some commit message"` or just `/yeet` to auto-generate the message. ## The Process ### Step 1: Stage All Files ```bash git add -A ``` ### Step 2: Show What Changed Run `git diff --cached --stat` and `git diff --cached` to show: - List of changed files with insertions/deletions - The actual diff content Present to user as a summary. ### Step 3: Detect Docs-Only Changes Run `git diff --cached --name-only` and treat the commit as docs-only only when every staged file ends in `.md` or `.txt`. - If the staged set is docs-only, mark that `yeet` should append `[skip ci]` to the final commit message. - If any staged file has a different extension, do not append `[skip ci]`. ### Step 4: Determine Commit Message - If the user provided a message, use it. - If no message was provided, check `git log --oneline -10` for recent commit style, then generate a concise commit message based on the diff. Use the **Conventional Commits** format: `type(scope): description` (e.g., `fix(auth): resolve token refresh race condition`, `feat(dashboard): add player search`). Common types: `feat`, `fix`, `refactor`, `style`, `docs`, `test`, `chore`, `perf`, `ci`, `build`. Scope is optional but preferred when the change is clearly scoped to a specific area. - If the staged set is docs-only, append ` [skip ci]` to the final commit message unless it is already present. ### Step 5: Confirm Ask user to confirm with a message like: ``` Ready to commit and push with message: "<message>" ``` Use `AskUserQuestion` with options "Yeet it" and "Cancel". ### Step 6: On Confirm ```bash git commit -m "<message>" git push ``` If push fails (no upstream), use `git push -u origin <current-branch>`. Report the commit hash and pushed branch when done. ### On Cancel ```bash git reset ``` Unstage everything and stop.
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.