skills.rest
matejformanek
matejformanekCOMMUNITY
Explore all skills by this author →
GitHub

meta-commit-style

Standardize commit message formatting for the postgres-claude meta-repository.

Updated Jun 1, 2026
Search Tags:#git#documentation#postgresql#commit#standardization#meta-repo
One-click install
npx skills add https://github.com/matejformanek/postgres-claude --skill meta-commit-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-commit-style
Source: https://github.com/matejformanek/postgres-claude/tree/main/.claude/skills/meta-commit-style
Command: npx skills add https://github.com/matejformanek/postgres-claude --skill meta-commit-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures consistency in the postgres-claude meta-repository by enforcing a specific commit message format that distinguishes meta-repo changes from upstream PostgreSQL patches.

Core Features & Use Cases

  • Structured Prefixes: Enforces specific prefixes like ft(corpus):, hf(scope):, and docs(scope): to categorize changes.
  • Trailer Management: Automates the inclusion of required trailers like Co-authored-by and Plan: links.
  • Use Case: When updating a knowledge corpus document or adding a new slash command, this skill guides the user to generate a commit message that aligns with the repository's established history and audit requirements.

Quick Start

Use the meta-commit-style skill to draft a commit message for the current changes in the postgres-claude repository following the required prefix and trailer conventions.

Frequently Asked Questions about meta-commit-style

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

FAQPage Schema
How do I standardize commit messages for a meta-repository?▼

Standardize commit messages for a meta-repository by applying specific prefix vocabulary, imperative title casing, and mandatory Co-authored-by footer trailers to distinguish changes from upstream patches.

What commit prefixes should I use for corpus updates and skill development?▼

Use structured prefixes like ft(corpus):, hf(scope):, and docs(scope): to categorize changes for corpus updates, skill development, and infrastructure modifications, ensuring repository auditability and consistency.

When do I need to include Co-authored-by trailers in my git commits?▼

Include Co-authored-by and Plan: link trailers in git commits whenever making non-upstream changes to the meta-repo, such as updating knowledge corpus documents or adding new slash commands.

Does this commit formatting approach work for upstream PostgreSQL patches?▼

No, this approach specifically excludes upstream PostgreSQL patches. It applies only to non-upstream changes within the meta-repository to separate internal modifications from the standard upstream history.

How do I draft a git commit message that aligns with established repository history?▼

Draft a git commit message by following required prefix and trailer conventions, using imperative title casing, and ensuring the message structure matches the repository's established history and audit requirements.

Related Skills

Explore More Software Engineering Skills→
rintirinti

code-review

Evaluate uncommitted git diffs with Codex CLI review feedback.

Community
Advanced
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
jpoutrinjpoutrin
14

git-commits

Enforce Conventional Commits format for Git commit messages.

Community
Basic
mattstrublemattstruble
2

git-commit

Analyze git history and staged changes to craft conventional commit messages.

Community
Advanced