Skip to content
Skills Library
Programming · Writing

git-style

/git-style

Prepare focused Git changes and clear commit messages, using Conventional Commits when the project has no other convention. Use when organizing a change, preparing a commit, or discussing Git workflow. Follow project branch and integration rules, and perform commits or remote actions only within the user's authorization.

Repository
anything ↗
Licence
Apache-2.0
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Prepare focused Git changes and clear commit messages, using Conventional Commits when the project has no other convention. Use when organizing a change, preparing a commit, or discussing Git workflow. Follow project branch and integration rules, and perform commits or remote actions only within the user's authorization.

Original author description

Prepare focused Git changes and clear commit messages, using Conventional Commits when the project has no other convention. Use when organizing a change, preparing a commit, or discussing Git workflow. Follow project branch and integration rules, and perform commits or remote actions only within the user's authorization.

How it works

  1. Understand the state
  2. Prepare focused changes
  3. Write the message
  4. Execute and report
Original SKILL.md headings · 58 lines, 435 words
SKILL.md preview
---
name: git-style
license: Apache-2.0
description: Prepare focused Git changes and clear commit messages, using Conventional Commits when the project has no other convention. Use when organizing a change, preparing a commit, or discussing Git workflow. Follow project branch and integration rules, and perform commits or remote actions only within the user's authorization.
---

# Git style

Follow the user's request and applicable project conventions. When no commit-message convention is established, use [Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/).

This skill needs Git only for Git operations. Without repository access, help draft the proposed change or message. Do not initialize a repository or install tools as a side effect.

## Understand the state

Inspect the relevant repository status, changes, and recent history when available. Identify the intended scope and existing conventions. Preserve unrelated edits and user work.

Choose branch and integration behavior from the task and project. This skill does not require a feature branch, worktree, merge commit, squash, or pull request.

## Prepare focused changes

- Keep each commit coherent enough to understand and review on its own.
- Stage only intended changes, using explicit paths or selected hunks as needed. Do not scoop up unrelated changes.
- Include necessary tests and documentation with the behavior they explain.
- Verify the affected result using the project's applicable checks. Report meaningful limits and unrelated failures.
- Do not fabricate an author, signature, issue reference, or attribution trailer. Use configured identity and required project metadata.

Preparing a change or message does not itself mean the user asked you to commit it.

## Write the message

Use this form by default:

```text
<type>[optional scope][!]: <summary>

<optional explanation>

<optional footers>
```

Use a short, concrete summary of the change. Include a scope when it helps identify the affected area. Explain the reason or non-obvious consequence in the body.

- `feat` introduces a feature; `fix` corrects a bug.
- Other useful types include `docs`, `refactor`, `test`, `perf`, `build`, `ci`, and `chore`. Follow the project's type set when it has one.
- Mark a breaking change with `!` before the colon or a `BREAKING CHANGE:` footer, and explain the compatibility impact.
- Add issue references and trailers only when applicable. Do not treat a local formatting preference as a requirement of the specification.

Examples:

```text
feat(search): filter results by tag
fix(parser): handle an empty input
docs: explain local installation
```

## Execute and report

Commit, push, publish, merge, rewrite history, or delete branches only when authorized for that effect. Reuse authorization within its scope; clarify a material change rather than re-asking about the same action. An approval-gate skill can help if installed, but is not required.

Respect protected branches and project integration policy. Avoid rewriting or discarding unrelated work. Cleanup needs its own applicable authorization and ownership check.

Verify the actual repository or remote result when an action is performed, then report it accurately. Do not claim a commit, push, or merge when you only prepared its contents.
Files in this package (3)
  • LICENSE.txt 11 KB
  • NOTICE 1 KB
  • SKILL.md 3 KB

Versions

The database has no other skills named git-style.

Database snapshot: 13.11.2026 · package version 119c7df1ddf6 (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

  • 100plei-git
    Write and review Git commit messages using Conventional Commits 1.0.0, or draft clear pull request descriptions for any project. Use when preparing commit messages or PR summaries; follow a repository's own conventions when they differ.
  • 100git-commit
    Inspect Git changes, organize logical commits, and write Conventional Commits messages. Use for /git-commit, explicit commit requests, message drafting, commit planning, and commit review. Excludes general Git troubleshooting, branch strategy, and history repair.
  • 100commit-message
    Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
  • 100git-workflow
    Conventional commits, PR creation, and quality gate verification. Use when: commit, PR, branch, push, conventional commit, create pull request, git.
  • 100commit-helper
    Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
  • 95git-commits
    Write clear, semantic git commit messages and PR/MR titles following Conventional Commits. Use when the user asks to write commit messages, format git history, improve commit quality, or set a PR/MR title, or mentions "commit message", "conventional commits", "merge message", or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.