Format, test, then commit with a conventional commit message
Scanned 9/12/2026
Install to Claude Code
npx -y skills add phel-lang/phel-pdo --skill commit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Commit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/phel-lang-commit)More formats (shields.io, HTML) on the badges page.
---
description: Format, test, then commit with a conventional commit message
argument-hint: "[optional commit message]"
disable-model-invocation: true
allowed-tools: "Read, Edit, Bash(composer *), Bash(./vendor/bin/phel *), Bash(vendor/bin/phel *), Bash(git *)"
---
# /commit
## Context
!`git diff --stat`
!`git diff --cached --stat`
!`git status --short`
## Instructions
1. **Format** - auto-format staged `.phel` files (no-op on non-Phel changes):
```bash
git diff --cached --name-only --diff-filter=ACMR | grep '\.phel$' | xargs -r vendor/bin/phel format
```
Note: a PostToolUse hook already runs `vendor/bin/phel format` on every Edit/Write - this step covers files staged from other tools.
2. **Test**:
```bash
composer test
```
Fix failures before continuing.
3. **Stage** specific files by name (never `git add -A`).
4. **Draft commit message**:
- Use `$ARGUMENTS` if given, else generate from the diff.
- Conventional commit prefixes: `feat:`, `fix:`, `ref:`, `chore:`, `docs:`, `test:`, `ci:`.
- Scope only when clearly scoped (`feat(statement)`, `fix(connection)`).
- Never mention AI tooling.
5. **Commit**: `git commit -m "<message>"`.
6. **Changelog check** - if `feat:` / `fix:`, warn when `## [Unreleased]` in `CHANGELOG.md` wasn't updated.
7. Report hash + files.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".