Create a git commit with optional automatic Linear issue linking. Use when the user asks to commit.
Run these commands to understand what's being committed:
git status
git diff --staged
git diff
If there are no staged changes, ask the user what to stage or suggest relevant files based on unstaged changes.
Use the Linear MCP tools to search for related issues:
List open issues in the Dinero.js project:
mcp__linear-server__list_issues with:
- project: "Dinero.js v2.0.0 Stable Release"
- state: "backlog" or "in_progress" or "todo"
Search by keywords from the changes (function names, file paths, feature areas)
Present matching issues to the user in a table:
| ID | Title | Status |
|---|---|---|
| SAR-110 | Restructure packages... | Backlog |
Ask the user using AskUserQuestion:
Options:
Generate a commit message following Conventional Commits format:
type(scope): subject
Description of changes.
[Fixes|Part of] SAR-XXX
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Types: feat, fix, docs, refactor, test, chore, style, perf Scopes: core, currencies, calculator-number, calculator-bigint, dinero.js, examples, docs, build, ci
git add -A)git status to confirm successmcp__linear-server__update_issuegit commit -m "$(cat <<'EOF'
feat(core): add subpath exports for currencies
Implemented exports field in package.json with proper TypeScript support
for all subpath entries.
Fixes SAR-111
Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"
git commit -m "$(cat <<'EOF'
refactor(core): extract currency types to separate module
First step in restructuring packages for consolidated dinero.js package.
Part of SAR-110
Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"
git commit -m "$(cat <<'EOF'