agentleFS
RostislavDuginRostislavDugin/postgresus/.agents/skills/git-commits/SKILL.md

git-commits

Skill9.1k starsChanged 42 days agoApache-2.0View on GitHub

Write Databasus commit messages and branch names using the repository's release-compatible format. Use when creating, editing or reviewing a commit message or branch name in this repository.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use one of these subject formats:

    line 8
  2. Very specific:

    Never use ! anywhere in the subject.

    line 14
  3. Distinctive:

    Keep the body to a short bullet list of what changed.

    line 16
  4. Distinctive:

    Keep the reasons and implementation details in OpenSpec.

    line 25
  5. Distinctive:

    Do not include co-author attribution unless the user requests it directly.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git commits

Use one of these subject formats:

  • FEATURE (scope): Summary
  • FIX (scope): Summary
  • REFACTOR (scope): Summary

Never use ! anywhere in the subject. The release workflow treats it as a breaking change and triggers a major version bump.

Keep the body to a short bullet list of what changed. Do not write long narrative paragraphs or hard-wrap lines at 80 characters. For example:

- validate PostgreSQL targets and quote conninfo values
- verify workspace access before applying saved credentials
- isolate local sockets and rotate internal database credentials
- add regression coverage and OpenSpec documentation

Keep the reasons and implementation details in OpenSpec. When a change has related OpenSpec files, commit them together with the implementation.

Name branches feature/<scope>, fix/<scope> or refactor/<scope>.

Do not include co-author attribution unless the user requests it directly.

Download now (ZIP)

Trending

Quiet since July.thin dataabout the whole repository

Dec 2025: 4 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the RostislavDugin/postgresus repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about RostislavDugin/postgresus

The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 10

Talked about on GitHub and Bluesky (10 times).

On GitHub · 7

2 more on GitHub

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.