New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git Commits

by romshark in romshark/datapages

Write Datapages commit messages, including the breaking-change marker and the BREAKING block.

MITAuto-check passedDevelopment

Install Git Commits

skills CLI
$ npx skills add romshark/datapages --skill git-commits -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install romshark/datapages git-commits --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/romshark/datapages.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/git-commits .claude/skills/git-commits && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-commits
GitHub stars
113
Token cost
~960 tokens
SKILL.md length
365 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Write Datapages commit messages, including the breaking-change marker and the BREAKING block.

  • Writing a commit message
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • A changelog entry

What it does

Git Commits is an agent skill from romshark/datapages. Write Datapages commit messages, including the breaking-change marker and the BREAKING block. Use when writing a commit message or a changelog entry.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. The repository describes itself as: A Datastar Go web frontend framework. The licence is MIT.

When your agent uses it

  • Writing a commit message
  • A changelog entry

Example prompts

  • “/git-commits”

What it can do on your machine

Read from SKILL.md and the folder at commit 87d5a44. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Commits loads about 960 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 365 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~960

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from romshark/datapages at commit 87d5a44, republished under its MIT licence (© romshark). 365 words, ~960 tokens.

Download SKILL.mdSave it as .claude/skills/git-commits/SKILL.md (or your agent's skills folder).
name
git-commits
description
Write Datapages commit messages, including the breaking-change marker and the BREAKING block. Use when writing a commit message or a changelog entry.

  • Respect writing.

  • Title: type: Summary, imperative, capitalized after the prefix, 50 characters or less, no trailing period.

  • Types: feat, fix, perf, refactor, test, chore, ci, docs. Suffix the type with ! for a breaking change.

  • Mark a change as breaking when it incompatibly changes an application-facing API. Changes to runtime/ APIs are not breaking: they are generator-facing, and datapages gen updates generated callers. Treat the root package, modules/ and generated APIs such as href and action as public APIs.

  • Wrap the description at 72 characters.

  • Imperative mood in the title, never past tense: Add cache, not Added cache or Adds cache. The description uses present tense and describes the code as it is now: Move foo to package buzz, not foo is now in package buzz. No first person, no we.

  • Don't paraphrase the code changes, the diff already shows them. The description is for what the diff can't show: why, scope, what was left out. Leave it empty when the title says everything.

  • Don't list the files touched, don't restate the title in longer words and don't close with a summary of the commit.

  • A commit that bundles several changes lists them as bullets, each with its own conventional prefix. List only the main changes. Tests, docs and call-site updates that come with a change are part of it, not separate bullets:

    feat: Add funcFoo <- keep, this is the change
docs: Add docs for funcFoo <- drop
test: Add tests for funcFoo <- drop
refactor: Use funcFoo everywhere <- drop
test: Add benchmark to test funcFoo against funcBar <- drop

  • A breaking change ends with a BREAKING: block. It is the migration instruction: name every removed or renamed symbol as old -> new, and say what the caller has to do, one step per line. A caller must be able to migrate from this block alone, without reading the diff. Say plainly when a step is automatic (datapages gen regenerates it) and when it is manual. Every line is a step the caller takes. Never list what did not change: href is unchanged is a step to do nothing. When a step could be read as reaching further than it does, narrow the step instead of adding a line: write EvSubjPref<Event> -> EvPrefix<Event>, the prefix constants only, not ... unchanged on a line of its own.

  • A perf: commit quotes the measurement as before -> after.

  • No tool attribution or Co-Authored-By trailers.

Show full SKILL.md (5 more words)Show less

Bad:

feat: added caching to the generator and updated some files

This commit adds a cache to the generator so that it is faster. I changed
internal/gen/gen.go, internal/gen/cache.go and internal/cmd/gen.go to add the
cache and wire it up. The cache stores parsed packages in a map keyed by import
path. Overall this makes the generator faster and cleaner.

Co-Authored-By: Some Tool <tool@example.com>

Good:

perf: Cache parsed packages in the generator

Every `datapages gen` run reparsed all dependencies. The cache keys on
import path and file mod time, which is safe because the loader already
rejects stale build artifacts.

Watch mode still reparses on every event: invalidation for edits inside
the module isn't implemented yet.

40ms -> 12ms on example/classifieds.

Good, breaking change:

refactor!: Move HTTP core to runtime packages

BREAKING:
- `datapages.NewCore` -> `runtime/httpserve.NewCore`.
- `datapages.CoreConfig` -> `runtime/httpserve.Config`.
- Generated code: run `datapages gen`, no hand edits needed.
- Hand-written callers: import `github.com/romshark/datapages/runtime/httpserve`
  and update the two names above.

© romshark, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/git-commits of romshark/datapages.

Open the folder on GitHubat commit 87d5a44

Compare with similar skills

Git Commits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Commits compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Commits this skillromshark/datapages113—~960Automated safety check: PassMIT
Contextual Commit Messagesyamadashy/repomix29k1 repos~2.7kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Caveman Commitvishiri/fantasia-archive40913 repos~642Automated safety check: PassGPL-3.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Contextual Commit Messages

    yamadashy/repomix

    Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.

    29k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Caveman Commit

    vishiri/fantasia-archive

    Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 13 repos~642 tokens
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from romshark/datapages

All 15 skills in this repo

  • Datapages

    romshark/datapages

    Apply the Datapages framework rules, build loop and naming conventions, and select the relevant task skill.

    113 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Datapages Events

    romshark/datapages

    Datapages real-time events: event types and subjects, dispatchers, On handlers, per-user and signal-bound subject fields, and the StreamOpen and StreamClose hooks.

    113 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Datapages Sessions

    romshark/datapages

    Add Datapages authentication: define and read the Session type, open and close sessions, configure CSRF protection and choose a session manager.

    113 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Datapages State

    romshark/datapages

    Add per-tab Datapages State[T], initialize and use it in handlers, dispatch state-scoped events, and configure the live instance limit.

    113 GitHub stars~806 tokensUpdated today
    Auto-check passed

  • Review Criteria

    romshark/datapages

    Classify Datapages findings by reach and severity and write review-.md reports.

    113 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Datapages Actions

    romshark/datapages

    Write Datapages action handlers (POST, PUT, PATCH, DELETE, QUERY): parameters, return values, Datastar signals, SSE patching, HTTP error status codes and the RecoverError hook.

    113 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Git Commits

What does Git Commits do?

Write Datapages commit messages, including the breaking-change marker and the BREAKING block. Git Commits is an agent skill from romshark/datapages. Write Datapages commit messages, including the breaking-change marker and the BREAKING block.

When should I use Git Commits?

Git Commits fits situations like: writing a commit message; A changelog entry.

How do I install Git Commits in Claude Code?

Run `npx skills add romshark/datapages --skill git-commits -a claude-code`. Or copy the skill folder (.claude/skills/git-commits in romshark/datapages) into .claude/skills/git-commits in your project. Claude Code loads it when a task matches its description.

How do I install Git Commits in Codex?

Run `npx skills add romshark/datapages --skill git-commits -a codex`. Or copy the skill folder (.claude/skills/git-commits in romshark/datapages) into .agents/skills/git-commits in your project. Codex loads it when a task matches its description.

Can I use Git Commits in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romshark/datapages --skill git-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-commits, .gemini/skills/git-commits, .github/skills/git-commits and .opencode/skills/git-commits in your project.

What does Git Commits need to run?

SKILL.md names no scripts, command-line tools or credentials: Git Commits is instructions for the agent only.

Does Git Commits access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Git Commits safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Commits use?

Git Commits is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Commits use?

About 960 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Commits?

Skills that share tags, products or a category with Git Commits: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Caveman Commit (vishiri/fantasia-archive, 409 stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Commits?

romshark (a GitHub user) maintains it in romshark/datapages, which has 113 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: romshark/datapages on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.