Agent skill

Commit Progress

by stellar in stellar/laboratory

Commit a logical unit of work with a descriptive message. An agent skill from stellar/laboratory.

Apache-2.0Auto-check: notesDevelopment

Install Commit Progress

skills CLI
$ npx skills add stellar/laboratory --skill commit-progress -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install stellar/laboratory commit-progress --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/stellar/laboratory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit-progress .claude/skills/commit-progress && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit-progress
GitHub stars
112
Token cost
~774 tokens
SKILL.md length
365 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Commit a logical unit of work with a descriptive message. An agent skill from stellar/laboratory.

  • Works in 4 steps: Assess what changed → Determine if changes form a coherent unit → Stage and commit → …
  • Development work in your project
  • SKILL.md covers When to Invoke, When NOT to Invoke, Procedure and Guidelines
  • Calls git

What it does

Commit Progress is an agent skill from stellar/laboratory. 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.

Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: A set of tools that enables developers to try out and learn about the Stellar network. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/commit-progress”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Assess what changed
  2. Determine if changes form a coherent unit
  3. Stage and commit
  4. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit b4b6465. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit Progress loads about 774 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 365 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~774

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:84
    - **Never commit** `.env`, credentials, or sensitive files

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from stellar/laboratory at commit b4b6465, republished under its Apache-2.0 licence (© stellar). 365 words, ~774 tokens.

Download SKILL.mdSave it as .claude/skills/commit-progress/SKILL.md (or your agent's skills folder).
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

Commit Progress

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.

When to Invoke

  • After a component is created and rendering correctly
  • After store fields/actions are wired and working
  • After tests are written and passing
  • After a bug fix is verified
  • After a refactor is complete
  • When switching context to a different sub-task

When NOT to Invoke

  • In the middle of incomplete work (half-written component, broken imports)
  • After only formatting or trivial changes
  • If there are no meaningful changes to commit

Procedure

1. Assess what changed

Run in parallel:

  • git status — see all modified/untracked files
  • git diff --stat — summary of changes
  • git diff — full diff of unstaged changes
  • git log --oneline -5 — recent commits for style reference
2. Determine if changes form a coherent unit

A good commit contains changes that serve one purpose. If the diff contains unrelated changes, stage only the related files.

Examples of coherent units:

  • "Add SignStepContent component and store fields"
  • "Wire simulate isNextDisabled logic"
  • "Add tracking events for sign step"
  • "Fix auth entry XDR parsing edge case"
Show full SKILL.md (176 more words)Show less
3. Stage and commit

Stage specific files (prefer explicit paths over git add .):

bash
git add src/app/(sidebar)/transaction/build/components/SignStepContent.tsx
git add src/store/createTransactionFlowStore.ts

Write commit message following the project's conventions:

  • Style: Informal, descriptive, present tense
  • Prefix: Use a context-aware prefix reflecting the feature/page (e.g., [Smart Contract Page], [View XDR], [New Tx], [Endpoints])
  • Format: Short summary line; no body needed for small changes
  • Examples from this repo:
    • [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 entries
    • fix auth entry parsing for empty credentials
bash
git commit -m "$(cat <<'EOF'
[New Tx] Add SignStepContent component

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"
4. Verify

Run git status to confirm clean state or expected remaining changes.

Guidelines

  • Never force push or amend without explicit user request
  • Never commit .env, credentials, or sensitive files
  • Never skip hooks (--no-verify) unless user explicitly requests it
  • Prefer small commits — if in doubt, commit more often
  • Pre-commit hook runs lint-staged (ESLint auto-fix on staged files) — if it fails, fix the lint error and create a NEW commit (don't amend)
  • Pre-push hook runs TypeScript check + all tests — these only run on push, not commit

© stellar, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/commit-progress of stellar/laboratory.

Open the folder on GitHubat commit b4b6465

Compare with similar skills

Commit Progress next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Progress compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Progress this skillstellar/laboratory112—~774Automated safety check: NotesApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from stellar/laboratory

  • Component Guide

    stellar/laboratory

    Guide for building React components using @stellar/design-system and project SCSS conventions.

    112 GitHub stars~999 tokensUpdated 4 days ago
    Auto-check passed
  • Correct mental models for React re-renders and memoization. An agent skill from stellar/laboratory.

    112 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • Zustand Store Patterns

    stellar/laboratory

    Reference for the two Zustand store patterns in Stellar Lab — main store (querystring) and transaction flow store (sessionStorage).

    112 GitHub stars~1.4k tokensUpdated 4 days ago
    Auto-check passed
  • Figma To Code

    stellar/laboratory

    Bridge Figma MCP output to Stellar Lab code conventions. An agent skill from stellar/laboratory.

    112 GitHub stars~520 tokensUpdated 4 days ago
    Auto-check passed
  • Test Changed

    stellar/laboratory

    Run e2e and unit tests related to files changed on the current branch.

    112 GitHub stars~836 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Commit Progress

What does Commit Progress do?

Commit a logical unit of work with a descriptive message. An agent skill from stellar/laboratory. Commit Progress is an agent skill from stellar/laboratory. Commit a logical unit of work with a descriptive message.

When should I use Commit Progress?

Commit Progress fits situations like: development work in your project.

How do I install Commit Progress in Claude Code?

Run `npx skills add stellar/laboratory --skill commit-progress -a claude-code`. Or copy the skill folder (.claude/skills/commit-progress in stellar/laboratory) into .claude/skills/commit-progress in your project. Claude Code loads it when a task matches its description.

How do I install Commit Progress in Codex?

Run `npx skills add stellar/laboratory --skill commit-progress -a codex`. Or copy the skill folder (.claude/skills/commit-progress in stellar/laboratory) into .agents/skills/commit-progress in your project. Codex loads it when a task matches its description.

Can I use Commit Progress in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stellar/laboratory --skill commit-progress -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-progress, .gemini/skills/commit-progress, .github/skills/commit-progress and .opencode/skills/commit-progress in your project.

What does Commit Progress need to run?

Going by SKILL.md and its folder, Commit Progress needs the command-line tools its instructions call (git).

Does Commit Progress access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit Progress safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit Progress use?

Commit Progress is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Progress use?

About 774 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Progress?

Skills that share tags, products or a category with Commit Progress: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Progress?

stellar (a GitHub organization) maintains it in stellar/laboratory, which has 112 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 3, 2026.

Source: stellar/laboratory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.