CtrlK
BlogDocsLog inGet started
Tessl Logo

pre-commit-checks

Pre-commit validation checks for azure-sdk-for-net. Use this before committing or pushing changes to SDK packages. Runs dotnet format, exports public API listings, updates snippets, and regenerates code as needed.

72

Quality

87%

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

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

A concrete, well-sequenced pre-commit workflow with real commands, explicit conditional triggers, and a final verification gate. It would benefit from per-step validation feedback loops and trimming the redundant 'Execution order' recap.

Suggestions

Add per-step validation checkpoints (e.g., after GenerateCode, confirm src/Generated/ changed as expected; after Export-API, diff the api/*.cs files) so failures are caught and retried immediately rather than only at the final step 6 gate.

Collapse the 'Execution order' section into a brief ordering note or a single ordered list, since the per-package vs per-ServiceDirectory scope is already stated in steps 1-5.

Clarify how a failed step should be remediated (fix and re-run just that step vs re-run the whole sequence) to turn the current 'do not commit if failed' guard into a true feedback loop.

DimensionReasoningScore

Conciseness

Lean, directive operational prose with no padding about concepts Claude already knows, but the 'Execution order' section partially restates per-step scope already covered in steps 1-5 and could be trimmed.

4 / 5

Actionability

Provides real executable commands (dotnet format, GenerateCode target, Export-API.ps1, Update-Snippets.ps1) plus concrete trigger conditions with specific file patterns and named CodeGen attributes; placeholders are well-defined in step 1.

5 / 5

Workflow Clarity

Clear sequencing with rationale and an end-to-end verification gate (step 6: check git status, do not commit if any step failed), but it lacks per-step validate-and-retry feedback loops for these batch/destructive regeneration operations.

4 / 5

Progressive Disclosure

Single well-organized file with numbered sections and no nested references; appropriate for a self-contained pre-commit checklist, though there is no overview-to-detail split since no bundle files exist.

4 / 5

Total

17

/

20

Passed

Description

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

A tight, well-targeted description that states a concrete purpose, explicit trigger timing, and four named actions for a specific SDK repo. Its only gap is trigger-term breadth (no synonyms or file extensions).

DimensionReasoningScore

Specificity

Lists four concrete actions ('Runs dotnet format, exports public API listings, updates snippets, and regenerates code'), matching the comprehensive multi-action anchor; only the trailing 'as needed' is mildly soft.

5 / 5

Completeness

Explicitly answers both what (the four checks) and when ('Use this before committing or pushing changes to SDK packages') with a concrete trigger phrase, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural triggers ('before committing or pushing changes', 'SDK packages', 'dotnet format', 'snippets'), but lacks synonyms and file extensions, so it is good rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'azure-sdk-for-net' pre-commit validation with repo-specific tooling, giving it a clear niche with minimal overlap risk against generic skills.

5 / 5

Total

19

/

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
Azure/azure-sdk-for-net
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.