commit

Standardize Git commit messages and branch names with approved prefixes.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill commit-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/OrestesK/pi/tree/main/skills/commit
Command: npx skills add https://github.com/OrestesK/pi --skill commit-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent Git commit messages and branch names by providing concise, predictable naming conventions without controlling Git permissions or operations.

Core Features & Use Cases

  • Commit Formatting: Apply approved prefixes, terse lowercase wording, and one-concern-per-commit guidance.
  • Branch Naming: Suggest branch names using the preferred ok/<short-topic> convention.
  • Presentation Guidance: Include relevant files and flag secrets, environment files, or unrelated changes when preparing commit-message suggestions.
  • Use Case: Use it when reviewing a proposed commit title or creating a branch name for a focused feature, fix, refactor, or maintenance task.

Quick Start

Use the commit skill to suggest a concise commit message and branch name for the current change.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write consistent git commit messages for refactors and maintenance tasks?

Standardize git commit messages by applying approved prefixes, using terse imperative lowercase wording, and ensuring one concern per commit. This approach covers features, fixes, refactors, and maintenance changes for a concise project history.

What is the best branch naming convention for focused feature work?

The recommended branch naming convention is ok/<short-topic>, which keeps branch names terse, clear, and consistent. It applies when creating branches for focused features, fixes, refactors, or maintenance tasks.

How should I format a commit message when preparing staged changes?

Format commit messages by including relevant files and flagging secrets, environment files, or unrelated changes. Apply approved commit prefixes with terse lowercase wording to maintain a predictable project history.

Can I use this to enforce Git permissions and block invalid operations?

No, this Skill strictly provides naming conventions and does not determine Git operation permissions. It suggests standardized commit messages and branch names without controlling or enforcing Git operations.

Why do my git branch names lack consistency across different code workflows?

Git branch names lack consistency without a standardized convention. Applying the ok/<short-topic> format ensures terse, predictable branch names across features, fixes, refactors, and maintenance changes.