conventions

Stars9

Forks0

UpdatedApril 25, 2026 at 07:22

Defines the commit message, branch naming, pull request, and release note conventions for the ai-agent-skills repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

psenger

psenger/ai-agent-skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

name	conventions
metadata	{"internal":true}
description	Defines the commit message, branch naming, pull request, and release note conventions for the ai-agent-skills repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.
allowed-tools	Read

Conventions — ai-agent-skills

Commit Messages

Format: type(scope): subject

Subject: imperative mood, lowercase, no trailing period, ≤72 characters
Scope: the skill name (vault-scribe, handoff) or a repo area (release, ci, readme)
Body: optional — explain why, not what; wrap at 72 chars
Footer: Closes #N or Fixes #N for GitHub issues; BREAKING CHANGE: <desc> for breaking changes

Types

Type	When
`feat`	New skill or new capability in an existing skill
`fix`	Bug fix in a skill's behaviour or instructions
`chore`	Release commits, tooling, config — no production change
`docs`	README, CHANGELOG, CONTRIBUTING only
`refactor`	Skill restructure with no behaviour change
`test`	Eval additions or changes

Release commit — always exactly:

chore(release): cut vX.Y.Z release

Examples

feat(handoff): add RESUME workflow and proactive suggestion trigger

fix(vault-scribe): prevent incompatible TOC directives

Closes #1

Branch Names

Pattern: type/issue-number-short-description

feature/14-add-handoff-skill
fix/23-vault-scribe-toc
chore/release-v1-1-0

feature/ for new skills or new capabilities
fix/ for bug fixes
chore/ for release and tooling work
Always include the issue number when one exists
2–4 words, hyphenated, no version dots (use dashes)

Pull Requests

Title: same format as a commit — type(scope): subject

Body:

## Summary
- <bullet 1>
- <bullet 2>

## Issue
Closes #N

## Test plan
- [ ] Skill activates on expected triggers
- [ ] Output matches documented format
- [ ] No regressions in adjacent skills

2–4 summary bullets
Always link the issue
Test plan as checkboxes

CHANGELOG Entries (Keep a Changelog 1.1.0)

### Added
- **skill-name** — What was added and why it matters. ([#N](url))

### Changed
- **skill-name** — What changed and the user-visible impact.

### Fixed
- **skill-name** — What was broken and what was fixed. ([#N](url))

Bold skill name, em dash, plain English, issue link at end
### Added for new skills, ### Changed for updates, ### Fixed for bugs
One bullet per logical change

Versioning

Semver from conventional commits since last tag:

Commit	Bump
`BREAKING CHANGE` or `type!:`	major
`feat`	minor
`fix`, `chore`, `docs`, `refactor`, `test`	patch

New skill = feat = minor bump. Tag format: vX.Y.Z (annotated tag).

More from this repository

same repository

git-commit-pr-message

psenger/ai-agent-skills

Generate git commit messages, PR titles/descriptions, and changelog entries. Analyzes staged changes, enforces Conventional Commits, scans for sensitive content, links tickets (GitHub Issues / Jira), and updates CHANGELOG.md. Triggers on: "commit", "create a PR", "push", "changelog", "release", or when the user is ready to commit or open a pull request.

2026-05-249

agent-os-profile-critique

psenger/ai-agent-skills

Provides the audit checklists, severity criteria (blocking/warning/suggestion), and artifact patterns needed to properly review Agent OS profiles and standards. Always invoke this skill before auditing - without it you can only give generic feedback, not structured severity-tagged findings. Invoke when the user pastes a standard and asks if it is good or what is wrong with it; when the user asks to review, audit, validate, or critique an agent-os profile or standard; or when the user mentions "agent-os profile", "agent-os standard", or "my agent-os setup" in a review or validation context.

2026-05-249

agentic-skeleton-dir-structure

psenger/ai-agent-skills

Scaffolds production-ready directory structures for agentic AI projects using Agent-OS v3 (Builder Methods). Use when the user asks to set up, scaffold, initialize, or restructure a project for agentic development — including mono-repos, single repos, multi-language repos, full-stack, backend, frontend, or middleware projects. Triggers on "scaffold directory", "project structure", "agentic scaffold", "project layout", "initialize AI project", "directory structure", "agent-os setup", "mono-repo layout", "IaC structure".

2026-05-249

vault-scribe

psenger/ai-agent-skills

Converts transcripts, video summaries, meeting notes, brainstorming sessions, strategy documents, and rough notes into polished Obsidian-flavored Markdown. Activates when creating or editing notes in an Obsidian vault, generating front matter, applying callout blocks, structuring knowledge base articles, or producing developer-facing guides. Also triggers on mentions of Obsidian, front matter, callout blocks, vault organisation, or requests for GitHub-compatible Markdown documents.

2026-05-249

export-vault-note

psenger/ai-agent-skills

Exports a single Obsidian vault note and all its linked images into a portable zip or tar.gz archive, preserving vault-root-relative paths so the archive unpacks correctly anywhere. Use only when the user explicitly invokes /export-vault-note.

2026-05-239

create-a-skill

psenger/ai-agent-skills

Create new agent skills from scratch, modify and improve existing skills, and measure skill performance through evaluation and benchmarking. Use when users want to create a skill, write a skill, build a new skill, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance, or optimize a skill's description for better triggering accuracy. Also triggers when users say "turn this into a skill", "make a skill for X", "skill for doing Y", or ask about skill structure, skill format, or SKILL.md files.

2026-05-169

name	conventions
metadata	{"internal":true}
description	Defines the commit message, branch naming, pull request, and release note conventions for the ai-agent-skills repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.
allowed-tools	Read

Conventions — ai-agent-skills

Commit Messages

Format: type(scope): subject

Subject: imperative mood, lowercase, no trailing period, ≤72 characters
Scope: the skill name (vault-scribe, handoff) or a repo area (release, ci, readme)
Body: optional — explain why, not what; wrap at 72 chars
Footer: Closes #N or Fixes #N for GitHub issues; BREAKING CHANGE: <desc> for breaking changes

Types

Type	When
`feat`	New skill or new capability in an existing skill
`fix`	Bug fix in a skill's behaviour or instructions
`chore`	Release commits, tooling, config — no production change
`docs`	README, CHANGELOG, CONTRIBUTING only
`refactor`	Skill restructure with no behaviour change
`test`	Eval additions or changes

Release commit — always exactly:

chore(release): cut vX.Y.Z release

Examples

feat(handoff): add RESUME workflow and proactive suggestion trigger

fix(vault-scribe): prevent incompatible TOC directives

Closes #1

Branch Names

Pattern: type/issue-number-short-description

feature/14-add-handoff-skill
fix/23-vault-scribe-toc
chore/release-v1-1-0

feature/ for new skills or new capabilities
fix/ for bug fixes
chore/ for release and tooling work
Always include the issue number when one exists
2–4 words, hyphenated, no version dots (use dashes)

Pull Requests

Title: same format as a commit — type(scope): subject

Body:

## Summary
- <bullet 1>
- <bullet 2>

## Issue
Closes #N

## Test plan
- [ ] Skill activates on expected triggers
- [ ] Output matches documented format
- [ ] No regressions in adjacent skills

2–4 summary bullets
Always link the issue
Test plan as checkboxes

CHANGELOG Entries (Keep a Changelog 1.1.0)

### Added
- **skill-name** — What was added and why it matters. ([#N](url))

### Changed
- **skill-name** — What changed and the user-visible impact.

### Fixed
- **skill-name** — What was broken and what was fixed. ([#N](url))

Bold skill name, em dash, plain English, issue link at end
### Added for new skills, ### Changed for updates, ### Fixed for bugs
One bullet per logical change

Versioning

Semver from conventional commits since last tag:

Commit	Bump
`BREAKING CHANGE` or `type!:`	major
`feat`	minor
`fix`, `chore`, `docs`, `refactor`, `test`	patch

New skill = feat = minor bump. Tag format: vX.Y.Z (annotated tag).