OpenParable
Skip to content
← Back to skills

Git Commit Message

Development
git-commit-message

Git Commit Message is an Agent Skill for development published in the werf/werf repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generates git commit messages according to werf conventions. Use after staging changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/werf/werf/blob/HEAD/.agents/skills/git-commit-message/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/git-commit-message, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Git Commit Message Generation

Instructions

  1. Read types, scopes, subject rules, and body rules from CONTRIBUTING.md#conventions.

  2. Analyze git diff --cached to determine the primary type and scope.

  3. Use the following format:

    <type>(<scope>): <subject>
    
    <body>
    
  4. Follow these rules:

    • Header: ≤ 72 characters. Nested scopes are allowed.
    • Subject: imperative, lower-case, no trailing period.
    • Body: imperative, include motivation for the change, contrast with previous behavior.
  5. Output ONLY the commit message (header + body), with no additional text, quotes, or formatting.