Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mise
Create a git commit with SR&ED (CRA tax credit) trailers. TRIGGERS - sred commit, sred, cra commit, tax credit commit, scientific research commit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mise:sred-commit [commit message summary][commit message summary]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a git commit with SR&ED (Scientific Research & Experimental Development) trailers for Canada CRA tax credit compliance.
Create a git commit with SR&ED (Scientific Research & Experimental Development) trailers for Canada CRA tax credit compliance.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
git diff --cached --stat
If nothing is staged, run git status and ask the user what to stage.
Write a commit message to /tmp/sred-commit-msg.txt following this format:
<type>(<scope>): <subject>
<body>
SRED-Type: <category>
SRED-Claim: <PROJECT-IDENTIFIER>
| Type | When to Use |
|---|---|
| feat | New feature or capability |
| fix | Bug fix |
| docs | Documentation only changes |
| style | Formatting, missing semicolons, etc. |
| refactor | Code change that neither fixes nor adds |
| perf | Performance improvement |
| test | Adding or correcting tests |
| build | Build system or external dependencies |
| ci | CI configuration files and scripts |
| chore | Maintenance tasks |
| revert | Reverting a previous commit |
| SRED-Type | CRA Definition |
|---|---|
| experimental-development | Achieving technological advancement through systematic work |
| applied-research | Scientific knowledge with specific practical application in view |
| basic-research | Scientific knowledge without specific practical application |
| support-work | Programming, testing, data collection supporting SR&ED activities |
Format: PROJECT[-VARIANT] (uppercase alphanumeric + hyphens).
To discover existing project identifiers in this repo:
git log --format='%(trailers:key=SRED-Claim,valueonly)' | sort -u | grep .
If no existing identifiers match, derive from the commit scope (e.g., feat(my-feature): → MY-FEATURE).
If unsure which SRED-Type or SRED-Claim to use, use AskUserQuestion to ask the user.
Run the validator on the draft message:
bun $HOME/.claude/plugins/marketplaces/cc-skills/plugins/itp-hooks/hooks/sred-commit-guard.ts --validate-message /tmp/sred-commit-msg.txt
Parse the JSON output:
{"valid": true} → proceed to commit{"valid": false, "errors": [...]} → fix the message and re-validate"discovery", present the suggestions to the user via AskUserQuestiongit commit -F /tmp/sred-commit-msg.txt
Using -F avoids shell quoting issues with special characters in commit messages.
rm -f /tmp/sred-commit-msg.txt
Show the user the commit hash and summary.
After this skill completes, reflect before closing the task:
Do NOT defer. The next invocation inherits whatever you leave behind.
npx claudepluginhub terrylica/cc-skills --plugin miseProvides Conventional Commits patterns for writing structured, machine-readable git commit messages with types, scopes, and breaking change indicators.
Generates conventional commit messages by analyzing staged Git changes. Helps write clear, standardized commit messages for version control.
Executes git commits with conventional commit message analysis, intelligent staging, and message generation. Use when asked to commit changes or when /commit is invoked.