SkillAgentSearch skills...

smart-commit

Run quality gates, review staged changes for issues, and create a well-crafted conventional commit

Install / Use

npx skills add rohitg00/pro-workflow --skill smart-commit

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

79/100

Category

Automation

Supported Platforms

Universal

Our assessment of smart-commit

smart-commit scores 79/100 on our quality scale, 2093rd of 2,659 Automation skills we index.

Its SKILL.md is 2.4 KB long, well organised into 9 sections with 2 code examples: moderately detailed.

With 2,876 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
20/30
Structure
18/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 6 days ago, so smart-commit is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

smart-commit compared with similar skills

All 4 of these similar skills score higher than smart-commit; compare them before choosing.

SkillScoreStarsUpdatedFormat
smart-commit (this skill)by rohitg00792.9k6d agoSKILL.md
Agent-Reachby Panniantong10086.4k15d agoCLAUDE.md
rufloby ruvnet10073.6ktodayCLAUDE.md
Scraplingby D4Vinci10084.6ktodayMCP Server
algorithmic-artby anthropics100177.9k7d agoSKILL.md

Frequently asked questions

How do I install smart-commit?
Run npx skills add rohitg00/pro-workflow --skill smart-commit. The install tabs above show the steps for each supported agent.
Which AI agents does smart-commit work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is smart-commit safe to use?
It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is smart-commit still maintained?
The repository was last updated 6 days ago, so smart-commit is actively maintained.

name: smart-commit description: Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes. user-invocable: true

Smart Commit

Trigger

Use when saying "commit", "save changes", or ready to commit after making changes.

Workflow

  1. Check current state and identify what to commit.
  2. Run quality gates (lint, typecheck, tests on affected files).
  3. Scan staged changes for issues.
  4. Draft a conventional commit message from the diff.
  5. Stage specific files, create the commit.
  6. Prompt for learnings from this change.

Commands

git status
git diff --stat

npm run lint 2>&1 | tail -5
npm run typecheck 2>&1 | tail -5
npm test -- --changed --passWithNoTests 2>&1 | tail -10

git add <specific files>
git commit -m "<type>(<scope>): <summary>"

Code Review Scan

Before committing, check staged changes in production code (not test files) for:

  • console.log / debugger statements (suppressed in test files — see Review Suppressions)
  • TODO/FIXME/HACK comments without ticket references (e.g., TODO(JIRA-123) is fine)
  • Hardcoded secrets or API keys
  • Leftover test-only code

Flag any issues before proceeding.

Commit Message Format

<type>(<scope>): <short summary>

<body - what changed and why>

Types: feat, fix, refactor, test, docs, chore, perf, ci, style

Guardrails

  • Never skip quality gates unless user explicitly says to.
  • Stage specific files by name. Never git add -A or git add ..
  • Summary under 72 characters. Body explains why, not what.
  • No generic messages ("fix bug", "update code").
  • Reference issue numbers when applicable.

Output

  • Quality gate results (pass/fail)
  • Issues found in staged changes
  • Suggested commit message
  • Commit hash after committing
  • Prompt: any learnings to capture?

Review Suppressions

Do NOT flag these during the pre-commit scan. They add noise without catching real bugs:

  • Threshold, config value, or feature flag changes (limits, timeouts, retry counts)
  • Import reordering that does not change runtime behavior
  • Whitespace-only or formatting-only changes
  • Adding or removing console.log in test files
  • TODO/FIXME comments (tracked separately in issue trackers)
  • Variable or parameter renames that do not change behavior

Related Skills

View on GitHub
GitHub Stars2.9k
CategoryAutomation
Updated6d ago
Forks289

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium