commit

What it does and when to use it

Prepare code for review by running quality checks, creating conventional commits, and opening pull requests. Use when the user wants to commit changes, create a PR, prepare for code review, or asks to commit their work.

How it works

1. 0. Branch Check
2. 1. Quality Assurance Checks
3. 2. Create Commits
4. 3. Create or Update Pull Request
5. 4. Report Results

---
name: commit
description: Prepare code for review by running quality checks, creating conventional commits, and opening pull requests. Use when the user wants to commit changes, create a PR, prepare for code review, or asks to commit their work.
disable-model-invocation: true
---

I'm getting ready for code review. Please follow these steps:

## 0. Branch Check
If you're on the `main` branch, create a new feature branch first before making any commits.

## 1. Quality Assurance Checks
Run the following commands in order:
1. bun run fmt
2. bun run lint
3. bun run check:ci
4. bun run knip
5. bun test

If any checks fail, address the issues before proceeding.

## 2. Create Commits
Split the file changes into logical commits following Conventional Commit format:
- `type(scope): message` (e.g., `feat(chat): add thread deletion`, `fix(auth): resolve token expiry`)
- Use types: feat, fix, refactor, docs, chore, test, etc.

Push all commits to the remote branch.

## 3. Create or Update Pull Request
Use the `gh` CLI tool to create or update the PR. The PR description MUST follow the structure defined in `.github/pull_request_template.md`.

**Important**: 
- Read `.github/pull_request_template.md` and follow its structure exactly
- Analyze the git diff and commits to generate accurate content for each section
- For "How to Test", provide specific, actionable steps based on the actual changes
- Mark "N/A" for Screenshots and Migration Notes if not applicable
- Ensure the PR title follows Conventional Commit format

## 4. Report Results
Finally, report the GitHub PR URL.

Versions

Database snapshot: 13.11.2026 · package version a470878fdc4d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 90commit-push
  Analyze changes, create categorized conventional commits, and push. Use when user asks to commit and push, invokes `/commit-push`, or requests conventional commits without a PR.
• 100commit-push-pr
  Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.
• 100branch-commit-pr
  Create a professionally named local git branch, commit the current changes in clean Conventional Commits (no Claude/AI signature), push it, and open a GitHub pull request. Use when the user asks to "make a branch and PR", "commit and open a PR", "ship these changes", or invokes /branch-commit-pr.
• 100creating-commit
  Creates context-aware git commits with smart pre-commit checks, submodule support, and conventional commit message generation. Use when user requests to commit changes, stage and commit, check in code, save work, save changes, push my code, finalize changes, add to git, create…
• 84create-pr
  Create or update pull requests with conventional commits. Use when user says "create a PR for these changes", "submit this for review", "open a pull request", "push these changes and create a PR", "I'm ready to submit this work", or "create PR and link to issue #123".
• 100git-commit
  Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples:…