skills.rest
pkuppens
pkuppensCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

integration-commit

Generate conventional commits referencing issues and apply them with git commit.

Updated Jan 5, 2025
Search Tags:#git#commit#quality-gate#issue-tracking#pull-request#conventional-commits
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill integration-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-commit
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/integration/integration-commit
Command: npx skills add https://github.com/pkuppens/pkuppens --skill integration-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating conventional commits that reference issues and follow repository conventions, reducing manual errors and improving traceability in the git history.

Core Features & Use Cases

  • Generates conventional commits that reference an issue and follow repo conventions.
  • Guides the user through staging changes and constructing a standardized commit message.
  • Integrates into the after-quality-gate workflow and before pushing and opening a PR.

Quick Start

Use the integration-commit skill to create and apply a conventional commit for the currently staged changes.

Frequently Asked Questions about integration-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a conventional commit that references an issue number?▼

To create a conventional commit referencing an issue, you format the message as '#NNN: type: short description'. This skill stages your intended changes and runs git commit -m to apply the standardized message.

When should I generate a conventional commit in my integration workflow?▼

You generate a conventional commit after your quality gate passes and before pushing or opening a pull request. This ensures only verified code changes are committed, improving git history traceability.

Does this conventional commit approach bypass pre-commit hooks?▼

No, this conventional commit approach does not bypass pre-commit hooks. It stages changes and applies the message using git commit -m, allowing your repository's pre-commit checks to run normally.

What is the correct format for a conventional commit message with issue tracking?▼

The correct format for a conventional commit message with issue tracking is '#NNN: type: short description'. This structure ensures your commits follow repository conventions and link directly to tracked issues.

How do I fix inconsistent git commit messaging across my pull requests?▼

You fix inconsistent git commit messaging by automating the generation of standardized messages. This skill constructs a conventional commit referencing your issue, reducing manual errors before pushing a pull request.

Related Skills

Explore More Software Engineering Skills→
mlhitermlhiter
14

git-commit-push

Automates git commit-and-push with conventional messages and safe publication to the remote branch.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
aldy505aldy505

commit

Generate Git commit messages following Sentry conventional commit standards.

Community
Intermediate
paulnsorensenpaulnsorensen
2

commit

Stage specific files and create conventional commits in Git.

Community
Intermediate