commit

Solid

Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says "commit", or before pushing a PR.

Code & Development 494 stars 68 forks Updated today AGPL-3.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Commit ## Planner Entry Stage and commit changes in the primary conversation after the task-defined implementation checks pass. Do not add broad post-commit `/verify` before push by default. Preserve the hook receipt as normal commit evidence. Create a git commit following this project's Conventional Commits convention. These messages are used by git-cliff (`cliff.toml`) to auto-generate changelogs and release notes. PRs are squash-merged, so the PR title becomes the commit on `main` — CI validates it via `pr-title.yml`. ## Available skills - **`/pr-fixup`** — Use after the PR opens only for CI or actionable reviewer findings. ## Format ``` type: lowercase description ``` ## Allowed Types | Type | Use for | In changelog? | |------|---------|---------------| | `feat` | New features | Yes (Features) | | `fix` | Bug fixes | Yes (Bug Fixes) | | `perf` | Performance improvements | Yes (Performance) | | `refactor` | Code refactoring | Yes (Refactoring) | | `docs` | Documentation changes | Yes (Documentation) | | `chore` | Maintenance, deps, configs | No | | `ci` | CI/CD changes | No | | `test` | Test-only changes | No | ## Rules - Subject **must** start with a lowercase letter - Scope is optional: `feat(ui): add dialog` is valid - Include PR/issue number when relevant: `feat: add release notes (#295)` - Breaking changes: add `!` after type: `feat!: remove legacy API` - Keep the first line under 72 characters - **Body lines must be ≤100 characters** (commitlint `body-...

Details

Author
kdlbs
Repository
kdlbs/kandev
Created
6 months ago
Last Updated
today
Language
Go
License
AGPL-3.0

Integrates with

Next.js · Frontend

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

commit

Commit staged changes with a clean, single-line Conventional Commit subject in plain developer English. Use when the user wants to commit changes, write a commit message, or wrap up work with a conventional-commit title. Generates a `type(scope): summary` subject from the staged diff and commits it. Triggers on phrases like 'commit this', 'make a commit', 'write a commit message', 'git commit', 'commit my changes'.

0 Updated 2 days ago
Srltas
Code & Development Listed

commit

Write a Conventional Commit from the actual staged diff and commit it. Use when the user asks to commit, or when work is done and needs committing.

0 Updated 4 days ago
2Tricky4u
Code & Development Listed

commit

Git commit workflow with conventional commits, branch creation, push, and PR support. Use when the user asks to commit, save changes, push, ship it, open a PR, send a PR, or says "/commit". Also triggers on short aliases: "cp" (commit and push), "cb" (commit to new branch), "cpr" (commit and PR). Trigger phrases: "commit", "commit and push", "commit new branch", "commit to new branch", "commit and pr", "commit push pr", "commit pr", "cp", "cb", "cpr", "push this up", "save my changes", "ship it".

0 Updated 4 days ago
svyatov