skills.rest
Fidasek009
Fidasek009COMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Creates git commits with concise messages, issue references, and model attribution.

1|Updated Dec 30, 2025
Search Tags:#git#code review#version control#commit#branching#issue tracking#commit message
One-click install
npx skills add https://github.com/Fidasek009/agents --skill commit-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Fidasek009/agents/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/Fidasek009/agents --skill commit-fidasek009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted commit messages is repetitive and often inconsistent across a team. This Skill inspects your staged changes and creates commits that follow repository conventions, include issue references, and protect sensitive data. ## Core Features & Use Cases - Convention-Aware Messages: Matches the recent commit style of the repository and keeps subjects short and specific. - Issue Linking & Attribution: Adds Fixes <issue> or Refs <issue> references and appends Co-Authored-By model attribution to every commit. - Safety Guardrails: Prompts before committing directly to main or master, strips PII and customer names from messages, and splits unrelated changes into separate commits. - Use Case: After fixing a login bug tracked as issue #42, ask the assistant to commit your changes and receive a commit like "Fix session timeout on token refresh" with Fixes #42 and proper co-author attribution. ## Quick Start Ask the assistant to commit the current changes with an appropriate message referencing the related issue.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a good git commit message automatically?▼

Inspect the staged diff and compose a short, specific subject line matching the repository's recent commit style. Add a body only for non-obvious context, and include issue references like Fixes #123 when resolving a known issue.

How to reference GitHub issues in commit messages?▼

Use "Fixes <issue>" in the commit message when the change resolves the issue, which closes it automatically on merge. Use "Refs <issue>" when the work is related but the issue remains open.

Should I commit directly to main or master branch?▼

Committing directly to main is risky for shared repositories. This Skill asks whether to commit on main or create a feature branch first, then follows your choice before creating the commit.

When should changes be split into multiple commits?▼

Split changes when they are unrelated, such as mixing a bug fix with a refactor or feature. Separate commits keep history readable, simplify code review, and make reverts safer.

How do I avoid leaking customer data in commit messages?▼

Replace customer names, user data, and PII with the technical symptom and issue ID before committing. This keeps the message informative while protecting sensitive information in permanent git history.

Related Skills

Explore More Software Engineering Skills→
codeaholicguycodeaholicguy
1.6k

dev-commit

Creates verified conventional git commits containing only intended changes.

Community
Intermediate
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
nateanatea

regression-testing

Automate regression test selection by change and risk in CI pipelines.

Community
Advanced
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate