// Commit a logical unit of work with a descriptive message. Invoke after completing a meaningful chunk (component created, store wired, tests passing) to maintain small, reviewable commits.
| name | commit-progress |
| description | Commit a logical unit of work with a descriptive message. Invoke after completing a meaningful chunk (component created, store wired, tests passing) to maintain small, reviewable commits. |
| user_invocable | true |
Create a focused commit for the work just completed. This skill produces small, reviewable commits — one per logical unit of work, not one per file edit.
Run in parallel:
git status — see all modified/untracked filesgit diff --stat — summary of changesgit diff — full diff of unstaged changesgit log --oneline -5 — recent commits for style referenceA good commit contains changes that serve one purpose. If the diff contains unrelated changes, stage only the related files.
Examples of coherent units:
Stage specific files (prefer explicit paths over git add .):
git add src/app/(sidebar)/transaction/build/components/SignStepContent.tsx
git add src/store/createTransactionFlowStore.ts
Write commit message following the project's conventions:
[Smart Contract Page], [View XDR], [New Tx], [Endpoints])[New Tx] Add Simulate Step[New Tx] Wire sign step into page layout[Smart Contract Page] Add contract deployment UI[View XDR] Fix XDR decoding for auth entriesfix auth entry parsing for empty credentialsgit commit -m "$(cat <<'EOF'
[New Tx] Add SignStepContent component
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"
Run git status to confirm clean state or expected remaining changes.
.env, credentials, or sensitive files--no-verify) unless user explicitly requests itGuide for building React components using @stellar/design-system and project SCSS conventions. Invoke when creating new components or reviewing component code.
Bridge Figma MCP output to Stellar Lab code conventions. Invoke after calling get_design_context to translate Figma's reference code into project-appropriate components, classes, and patterns.
Correct mental models for React re-renders and memoization. Use this skill when writing, reviewing, or optimizing React components to avoid common misconceptions about performance. Debunks the myth that "props cause re-renders" and teaches when memoization actually helps.
Reference for the two Zustand store patterns in Stellar Lab — main store (querystring) and transaction flow store (sessionStorage). Invoke when creating store slices, debugging hydration, or deciding where state belongs.
Run e2e and unit tests related to files changed on the current branch. Use after making code changes to verify nothing is broken.