Always invoke this skill for any git-related request (commit messages, staging review, history, PR descriptions, etc.) so git workflows are handled consistently.
80
71%
Does it follow best practices?
Impact
93%
1.34xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./git-workflow/SKILL.mdCommit message file format and output location
Output file location
0%
100%
Conventional commit type
100%
100%
Conventional commit subject line
100%
100%
Commit body present
100%
100%
History loaded before draft
100%
100%
Review: critical issues category
0%
100%
Review: suggestions category
0%
100%
Review: questions category
0%
0%
Staged diff examined
100%
100%
No hardcoded secret flagged
100%
100%
cache dir created
0%
100%
Pull request description structure and content
Summary section present
100%
100%
Summary is concise
100%
100%
Key Changes section present
0%
100%
Key Changes is a bullet list
0%
100%
Key Changes includes file names
0%
100%
Commit History section present
100%
100%
Commit hashes in history
100%
100%
Commits are chronological
100%
100%
Diff collected from main
40%
0%
Commit messages collected from main
60%
100%
PR description saved to file
100%
100%
Staged changes review categories and summary format
Critical issues section
100%
100%
Suggestions section
100%
100%
Questions section
0%
100%
Security: hardcoded secret flagged
100%
100%
Security: SQL injection flagged
100%
100%
Logic: off-by-one error flagged
100%
100%
Code quality: deeply nested code flagged
100%
87%
Style: inconsistencies flagged
100%
100%
Missing pieces: error handling flagged
100%
100%
Staged diff examined
75%
75%
Severity distinction
100%
100%
1462f26
Table of Contents
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.