Analyzes git changes, groups them by logical change or OpenSpec feature, and creates conventional commits for each group.
91
Quality
89%
Does it follow best practices?
Impact
94%
1.02xAverage score across 5 eval scenarios
Multi-feature commit grouping
Plan before staging
100%
100%
Auth group identified
100%
100%
Payments group identified
100%
100%
Infra/CI group identified
100%
100%
Multiple commits made
100%
100%
Conventional commit type: feat
100%
100%
Conventional commit type: chore
50%
100%
Scope is short and logical
100%
100%
Action verb in description
100%
100%
No file listing in messages
100%
100%
Line length ≤ 72 chars
100%
100%
git log shown at end
100%
100%
OpenSpec feature-based scope naming
customer-import scope used
100%
100%
audit-log scope used
100%
100%
Two separate feature commits
100%
100%
customer-import spec grouped with impl
100%
100%
audit-log spec grouped with impl
100%
100%
Conventional commit type: feat
100%
100%
Correct conventional format
100%
100%
Action verb in description
100%
100%
Line length ≤ 72 chars
50%
100%
No file listing in messages
100%
100%
git log captured
100%
100%
Feature commits ordered before any others
100%
100%
Conventional commit message format
Single commit for one logical unit
100%
100%
Conventional commit type: feat
100%
100%
Scope present and short
0%
100%
Action verb starts description
100%
100%
No file names in message
100%
100%
Describes intent, not implementation
100%
50%
Line length ≤ 72 chars
100%
0%
Correct conventional format
50%
100%
No layer enumeration in scope
100%
100%
git log captured
100%
100%
Message is one line
100%
100%
Large mixed codebase organization
Multiple commits created
100%
100%
Notifications grouped together
100%
100%
Reporting grouped together
100%
100%
Infra grouped separately
100%
100%
Docs type used for documentation
100%
100%
Feat type for features
100%
100%
Chore or feat type for infra
0%
100%
Plan before committing
100%
100%
No file listing in messages
100%
75%
Concise descriptions
100%
100%
Line length ≤ 72 chars
100%
66%
Action verb in each message
100%
100%
Workflow sequence and staged review
Status check logged
100%
100%
Diff analysis before staging
0%
100%
Staged diff reviewed
100%
100%
Explicit file list in git add
100%
100%
Two separate commits
100%
100%
Refactor type for db changes
100%
100%
Docs type for contributing guide
100%
100%
git log run at end
100%
100%
Action verb in descriptions
100%
100%
Line length ≤ 72 chars
100%
50%
No file listing in messages
100%
0%
Install with Tessl CLI
npx tessl i spec-driven-magic/sdx-commit@0.1.1