Creates git commits with Conventional Commits-style subjects from staged changes.
npx skills add https://github.com/davidsunglee/pi-flow --skill commit-davidsunglee
Please help me install this Agent Skill. Skill: commit Source: https://github.com/davidsunglee/pi-flow/tree/main/packages/pi-flow-core/skills/commit Command: npx skills add https://github.com/davidsunglee/pi-flow --skill commit-davidsunglee
<type>(<scope>): <summary> format with types like feat, fix, docs, and refactor. - Selective Staging: Honors caller-provided file paths or globs to limit which changes get committed, and asks for clarification when files are ambiguous. - Scope Inference: Optionally reviews recent commit history (git log) to reuse commonly used scopes for consistency. - Use Case: After finishing a bug fix across several files, ask for a commit and receive a properly formatted message like fix(parser): handle empty input tokens with only the intended files staged. ## Quick Start Ask the assistant to commit the current changes with a concise conventional commit message, optionally specifying files or extra instructions.High-intent search queries and answers about installing and using this skill.
Use the format `<type>(<scope>): <summary>`, where type is required (such as feat or fix), scope is an optional short noun in parentheses, and summary is an imperative phrase under 72 characters with no trailing period.
Provide file paths or globs along with your commit request, and only those files will be staged and committed. If it is unclear whether a file should be included, you will be asked which files to commit before proceeding.
No, it only creates the local commit and never pushes. It also omits sign-off trailers and breaking-change footers, keeping the commit limited to a subject and an optional body.
Use `feat` for new features and `fix` for bug fixes as the primary types. Other common types include `docs`, `refactor`, `chore`, `test`, and `perf`, chosen based on the nature of the change.
Running `git log -n 50 --pretty=format:%s` reveals commonly used scopes in the repository. Reusing existing scopes keeps the commit history consistent and makes changelogs and searches more reliable.
antoniocascaisAnalyze git diffs to assess code quality, security, and merge readiness.
santychuycomAnalyze diffs, create atomic conventional commits, push, and open pull requests.
owenlamontAutomate Python code linting and formatting with pre-commit hooks.
relaticleApply Spatie's Git conventions to commits, branches, and pull requests.