prp-commit

Quick commit with natural language file targeting. Use when the user wants to commit changes, stage and commit specific files, or invokes $prp-commit.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable commit workflow with executable commands and clean phasing. The main gap is the absence of an explicit pre-commit verification checkpoint and a commit-failure recovery loop for what is a destructive/batch operation.

Suggestions

Add an explicit verification checkpoint in Phase 2/3, e.g. after `git diff --cached --name-only`, instruct Claude to confirm the staged set matches the user's intent before committing.

Add a feedback loop for commit failures (e.g. on a non-empty pre-commit hook rejection, surface the error, fix, and re-commit) so the workflow matches the anchor-3 validation pattern.

Clarify the vague 'the X changes → Interpret from diff/context' table row with a concrete default action so every input maps to an executable command.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line mission, a compact input→action table, and bare git commands with no explanation of concepts Claude already knows; every section earns its tokens.	3 / 3
Actionability	It gives concrete, executable commands ('git status --short', 'git add -A', 'git diff --cached --name-only', 'git commit -m "{type}: {description}"') plus a literal input→command table and a copy-paste output template.	3 / 3
Workflow Clarity	Phases are clearly sequenced and Phase 1 stops on an empty tree, and Phase 2 shows staged files before committing; however there is no explicit verification step ('confirm the staged set is intended') and no error-recovery loop for a failed commit, which caps destructive/batch operations at 2 per the rubric guideline.	2 / 3
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with no need for external references; the body is well-organized into labeled phases, a table, and examples, which satisfies the simple-skill allowance for a top score.	3 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, concise description that answers both what and when with natural trigger terms and a distinct invocation hook. Its only weakness is that the capability list is thin — it names stage/commit but does not lay out multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Names the commit domain and some actions ('stage and commit specific files', 'natural language file targeting') but does not enumerate multiple distinct concrete actions like the anchor-3 example does; 'natural language file targeting' reads as a feature rather than an action.	2 / 3
Completeness	It states both what it does ('Quick commit with natural language file targeting') and when to use it ('Use when the user wants to commit changes...'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	'the user wants to commit changes, stage and commit specific files' are natural phrases users would actually say, and the explicit '$prp-commit' invocation covers the command-trigger case.	3 / 3
Distinctiveness Conflict Risk	The 'natural language file targeting' angle plus the explicit '$prp-commit' invocation give it a clear niche distinct from a generic git skill, making false-trigger conflict unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Wirasm/prp
Path: .agents/skills/prp-commit/SKILL.md
Commit: 1142738

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.