Run git status, git diff (staged + unstaged), and git log --oneline -10.
Group changes into logical units. Each unit becomes one atomic commit — a single bug fix, feature, refactor, or config change. Files that must go together for correctness belong in the same commit. Prefer small, focused commits — split aggressively by logical unit.
- If the commit message has the word "and", that is a commit-split signal.
Create commit for the defined groups:
- Stage only the relevant files by name. Never git add -A or git add ..
- If a file has changes belonging to different commits, stage only the relevant hunks or lines for each commit. Prefer splitting by hunk over grouping the whole file into one commit when it produces more semantically accurate commits.
- Commit using a HEREDOC. Never add Co-Authored-By trailers.

Commit messages

Conventional Commits: type: short description. No scope in parentheses.
Single line only — no body, no footer.
Imperative mood, lowercase, no period, under 72 chars.

Más de este repositorio

mismo repositorio

review-pr

p2kmgcl/chachi-shell

Reviews a GitHub PR and creates a pending review with editorially gated inline/body findings. Use when the user asks to review a PR or create a draft GitHub review.

2026-07-016

local-rules

p2kmgcl/chachi-shell

Load machine-local rule overrides for a given skill from the shared ~/.agents skills directory.

2026-06-026

create-ticket

p2kmgcl/chachi-shell

Create a JIRA ticket interactively — gathers requirements through conversation, proposes the ticket, and creates it after approval

2026-06-026

grill-with-docs

p2kmgcl/chachi-shell

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

2026-06-026

handoff

p2kmgcl/chachi-shell

Compact the current conversation into a handoff document for another agent to pick up.

2026-06-026

improve-codebase-architecture

p2kmgcl/chachi-shell

Find deepening opportunities in a codebase, informed by the domain language in .agent-state/CONTEXT.md and the decisions in .agent-state/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

2026-06-026

name	commit
description	Create one or more atomic commits from current changes, grouping by logical unit

Run git status, git diff (staged + unstaged), and git log --oneline -10.
Group changes into logical units. Each unit becomes one atomic commit — a single bug fix, feature, refactor, or config change. Files that must go together for correctness belong in the same commit. Prefer small, focused commits — split aggressively by logical unit.
- If the commit message has the word "and", that is a commit-split signal.
Create commit for the defined groups:
- Stage only the relevant files by name. Never git add -A or git add ..
- If a file has changes belonging to different commits, stage only the relevant hunks or lines for each commit. Prefer splitting by hunk over grouping the whole file into one commit when it produces more semantically accurate commits.
- Commit using a HEREDOC. Never add Co-Authored-By trailers.

Commit messages

Conventional Commits: type: short description. No scope in parentheses.
Single line only — no body, no footer.
Imperative mood, lowercase, no period, under 72 chars.