CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An efficient, actionable, well-sequenced skill body that wastes no tokens and gives Claude everything needed to commit with natural-language file targeting. The only minor gap is the absence of a post-commit verification step, but the pre-commit guards keep it strong.

DimensionReasoningScore

Conciseness

Lean throughout with no concept-explaining fluff; every section (phases, interpretation table, examples) earns its tokens and assumes Claude's competence.

3 / 3

Actionability

Provides fully executable commands (git status --short, git add -A, git diff --cached --name-only, git commit -m) plus a concrete target-interpretation table — copy-paste ready guidance.

3 / 3

Workflow Clarity

Clear four-phase sequence (ASSESS, INTERPRET & STAGE, COMMIT, OUTPUT) with an explicit early checkpoint ('If nothing to commit, stop') and a show-staged-files step before committing.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized labeled sections and no need for external references; meets the simple-skill threshold for a top score.

3 / 3

Total

12

/

12

Passed

Description

92%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 concise, well-structured description that covers what and when with explicit, natural trigger terms. Its only weakness is moderate overlap with general git/commit skills before the slash-command trigger is considered.

Suggestions

Add a more distinctive noun or scope (e.g. 'lightweight /prp-commit helper' or 'opinionated single-line commits') to reduce overlap with general git-commit skills.

Consider mentioning the message style (imperative, conventional-commit types) in the description to further differentiate from a plain 'git commit' skill.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Quick commit', 'stage and commit specific files', 'natural language file targeting' — rather than vague abstractions.

3 / 3

Completeness

Clearly answers both what it does (quick commit with NL file targeting) and when to use it via an explicit 'Use when the user wants to commit changes...' clause.

3 / 3

Trigger Term Quality

Includes natural phrases users would actually say ('commit changes', 'stage and commit specific files') plus the explicit '/prp-commit' invocation trigger.

3 / 3

Distinctiveness Conflict Risk

The commit domain is broadly applicable and 'commit changes' could overlap with general git skills; the '/prp-commit' trigger narrows it but the natural-language triggers are not fully distinctive.

2 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
Reviewed

Table of Contents

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.