CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-commit

Creates Git commits for completed work. Always use when committing changes, when the user explicitly asks to commit the work, when another PRP workflow reaches its commit step, or when the user invokes $prp-commit.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/prp-commit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

The content is concise and well-structured for a single-purpose commit skill, with concrete scoping rules and an explicit verification step. It is slightly short on explicit error-recovery feedback loops and exact commands.

DimensionReasoningScore

Conciseness

Lean, well-organized prose that assumes Claude's competence; every line adds specific guidance about scoping, messaging, and verifying commits with no padding or basic-Git explanations.

5 / 5

Actionability

Provides concrete, executable guidance (inspect staged/unstaged/untracked, split vs. preserve, verify content/exclusion/untouched state, return hash+message+scope) with minor gaps for an instruction-only skill lacking exact commands.

4 / 5

Workflow Clarity

Clear sequenced sections with an explicit verification checkpoint ("Verify the resulting commit contains every intended change, excludes unrelated changes, and leaves the remaining worktree state untouched") and a stop-and-ask guardrail, though error-recovery feedback loops are only implicit.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Scope, Message, Commit and verify) and no external references needed, matching the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

73%Weight 40%Scale 1-5

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

The description is strong: it clearly states the skill's purpose and provides multiple explicit, natural trigger conditions plus a unique invocation token. The only minor gap is capability breadth beyond the single "creates commits" action.

DimensionReasoningScore

Specificity

Names the Git-commit domain and the concrete action "Creates Git commits for completed work" but offers only that one action, with no enumeration of broader capabilities, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

Explicitly states what it does (creates Git commits for completed work) and gives concrete "when" trigger phrases including user requests, workflow handoffs, and skill invocation.

5 / 5

Trigger Term Quality

Covers natural user phrasings ("committing changes", "asks to commit the work") plus the invocation token $prp-commit, giving good keyword coverage though a few common synonyms like "save" or "checkpoint" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to PRP-workflow commits with distinct triggers and an explicit $prp-commit invocation token, minimizing overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.