dinerojs/dinero.js · Archived

commit

Create a git commit with optional automatic Linear issue linking. Use when the user asks to commit.

First seen Mar 1, 2026

Installation

$ npx skills add dinerojs/dinero.js --skill commit

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dinerojs/dinero.js.

npx skills add dinerojs/dinero.js

Browse all from dinerojs/dinero.js

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6.8K
License LICENSE
Default branch main
Open issues 3
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,666 B
  • docs SUMMARY.md 113 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Workflow

Step 1: Analyze Changes

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.

Step 2: Find Related Linear Issues

Use the Linear MCP tools to search for related issues:

  1. List open issues in the Dinero.js project:

`` mcplinear-serverlistissues with: - project: "Dinero.js v2.0.0 Stable Release" - state: "backlog" or "inprogress" or "todo" ``

  1. Search by keywords from the changes (function names, file paths, feature areas)
  1. Present matching issues to the user in a table:
ID Title Status
SAR-110 Restructure packages... Backlog

Step 3: User Selection

Ask the user using AskUserQuestion:

  • Which issue(s) does this commit relate to?
  • Does this commit complete the issue (Fixes) or is it partial progress (Part of)?

Options:

  • Select from found issues
  • Enter a different issue ID
  • No Linear issue (skip linking)

Step 4: Create Commit

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

Step 5: Execute

  1. Stage files if needed (prefer specific files over git add -A)
  2. Create the commit using a HEREDOC for proper formatting
  3. Run git status to confirm success
  4. If the commit completes an issue, offer to update it in Linear using mcplinear-serverupdate_issue

Examples

Completing an issue

git 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
)"

Partial progress

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
)"

No Linear issue

git commit -m "$(cat <<'EOF'
chore: update .gitignore

Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"