skills.rest
lhohan
lhohanCOMMUNITY
Explore all skills by this author →
GitHub

agentfiles-commit-prefixes

Enforce area prefixes on commit messages across agentfiles packages.

Updated Apr 14, 2026
Search Tags:#git#commit#agents#version-control#repository-guidelines#area-prefix
One-click install
npx skills add https://github.com/lhohan/agentfiles --skill agentfiles-commit-prefixes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentfiles-commit-prefixes
Source: https://github.com/lhohan/agentfiles/tree/main/.agents/skills/agentfiles-commit-prefixes
Command: npx skills add https://github.com/lhohan/agentfiles --skill agentfiles-commit-prefixes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages across this repository often lack clear scope, making reviews slower and changes harder to track across multiple packages.

Core Features & Use Cases

  • Enforces area-prefixed commit subjects to communicate the affected package or component.
  • Provides a reference mapping for prefixes (pi:, dotagents:, shared:, docs:, build:, chore:).
  • Use case: when updating agents/pi, agents/dotagents, or agents/agents-shared, apply the appropriate prefix to the subject line.

Quick Start

Write your next commit subject using the form '<prefix>: <imperative summary>' to indicate the affected area.

Frequently Asked Questions about agentfiles-commit-prefixes

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

FAQPage Schema
How do I standardize git commit messages across multiple packages?▼

Area prefixes in commit messages indicate the affected package scope, such as 'pi:' or 'docs:'. They make package ownership immediately clear and help reviewers track changes across multi-package repositories by grouping commits by component.

What prefixes should I use for commits affecting shared packages?▼

Use the 'shared:' prefix for commits affecting agents-shared packages. The enforced prefix list also includes 'pi:', 'dotagents:', 'docs:', 'build:', and 'chore:' to map standard commit subjects to their respective repository areas.

How do I format commit subjects for multi-package repository changes?▼

Format commit subjects as '<prefix>: <imperative summary>' to indicate the affected area. This structure clarifies scope across multi-package changes and requires updating the prefix mapping when new packages are added to the repository.

When should I update the commit prefix mapping for new packages?▼

Update the commit prefix mapping when adding new packages to the repository. This maintains accurate scope tracking across all commits, ensuring the fixed prefix list reflects the current package structure and ownership boundaries.

Why do commit messages need area prefixes in version control?▼

Area prefixes are needed because unscoped commit messages make reviews slower and changes harder to track across multiple packages. Prefixes like 'build:' or 'chore:' immediately clarify the scope and package ownership of each modification.

Related Skills

Explore More Software Engineering Skills→
stephendolanstephendolan
2

writing-git-commits

Draft conventional git commit messages with type, scope, and summary.

Community
Basic
SynkraAISynkraAI
3.1k

aios-devops

Manage GitHub repositories and automate CI/CD workflows with quality gates.

Official
Advanced
faustellar1995faustellar1995
1

commit

Analyze staged git changes to draft commit messages.

Community
Intermediate
itzcullitzcull
3

git-conventions

Define conventional commit types and TDD-style commit rhythms for software projects.

Community
Advanced