commit

Included with Lifetime

$97 forever

Review, stage, commit, and push all current changes to remote.

Code Review

What this skill does

# Commit & Push

Review, stage, commit, and push the current changes.

## Workflow

Execute these steps in order.

### 1. Review All Changes

```bash
git status
git diff
git diff --staged
```

Before committing, check for:

- **Nothing to commit** — if `git status` shows a clean tree, stop and tell the user.
- **Debug statements** (e.g. `console.log`, `dbg!`, stray `print` calls) added during the session
- **Commented-out code** that shouldn't ship
- **Secrets** — `.env`, keys, tokens, passwords
- **Unintended files** — editor backups, large binaries, scratch dirs

If anything is suspicious, stop and ask the user before proceeding.

### 2. Stage Specific Files

Prefer explicit paths over `git add .` or `git add -A` — blanket staging can silently pick up `.env` files, local scratch work, or other unintended files.

```bash
git add <path1> <path2> ...
```

If every tracked change is in-scope and there are no risky untracked files, `git add .` is fine — but only after you've looked at `git status` and confirmed.

### 3. Write the Commit Message

**Format:**

```
<ticket>: <summary>

- What changed and why
- Group related changes
- Focus on intent, not mechanics
```

**Guidelines:**

- **Ticket is optional.** Extract a ticket from the branch name if one is present (e.g. `feature/eb-1250-...` → `EB-1250: <summary>`). If the branch has no ticket, skip the prefix and write `<summary>` directly.
- Summary ≤ 72 characters, imperative mood ("Add X" not "Added X")
- Bullet points explain the *why* when it isn't obvious from the diff

**Examples:**

With a ticket:
```
EB-1250: Add user authentication flow

- Implement login form with email/password validation
- Add JWT token handling in auth service
- Create protected route wrapper component
```

Without a ticket:
```
Replace hardcoded base branch with git auto-detection

- Read origin/HEAD to pick the trunk branch at runtime
- Fall back to probing dev/main/master locally
```

### 4. Commit

For multi-line messages, use a HEREDOC so quoting is safe:

```bash
git commit -m "$(cat <<'EOF'
<summary line>

- <bullet>
- <bullet>
EOF
)"
```

**If a pre-commit hook fails:** the commit did NOT happen. Fix the issue, re-stage, and create a **new** commit. Never use `--amend` here — there is no previous commit from this run to amend; `--amend` would modify the commit that came before.

### 5. Push

```bash
git push -u origin "$(git branch --show-current)"
```

The `-u` flag is harmless if the upstream is already set — it only sets tracking on first push.

### 6. Confirm

Report to the user:

- The commit hash and summary line
- The branch name and that the push succeeded

Files: 1

Size: 2.7 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/finstreet/fe-claude-plugins/tree/main/plugins/finstreet-dev/skills/commit

Related in Code Review

gstack

Included

Fast 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)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal 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.

Code Reviewscripts

interview-master

Included

This 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.

Code Reviewscripts

fix-issue

Included

Fixes 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.

Code Reviewscripts

sf-apex

Included

Generates 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.

Code Reviewscripts

swift-development

Included

Comprehensive 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.

Code Reviewscripts