MCPInstall

oma-commit

Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.

Installs
105
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/gracefullight/stock-checker --skill oma-commit
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads oma-commit automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Commit Skill - Conventional Commits

When to use

  • When user requests "commit this", "commit", "save changes"
  • When /commit command is invoked

Configuration

Project-specific settings: .agents/skills/commit/config/commit-config.yaml

Commit Types

TypeDescriptionBranch Prefix
featNew featurefeature/
fixBug fixfix/
refactorCode improvementrefactor/
docsDocumentation changesdocs/
testTest additions/modificationstest/
choreBuild, configuration, etc.chore/
styleCode style changesstyle/
perfPerformance improvementsperf/

Commit Format

<type>(<scope>): <description>

[optional body]

Co-Authored-By: First Fluke <our.first.fluke@gmail.com>

Workflow

Step 1: Analyze Changes

git status
git diff --staged
git log --oneline -5

Step 1.5: Split by Feature (if needed)

If changed files span multiple features/domains, split commits by feature.

Split criteria:

  • Different scopes (e.g., workflows vs skills vs docs)
  • Different types (e.g., feat vs fix vs docs)
  • Logically independent changes

Example:

# Changed files:
.agents/workflows/*.md (7 files)     → fix(workflows): ...
.agents/skills/**/*.md (4 files)     → fix(skills): ...
USAGE.md, USAGE-ko.md               → docs: ...

# Split into 3 commits

Do NOT split when:

  • All changes belong to a single feature
  • Few files changed (5 or fewer)
  • User requested a single commit

Step 2: Determine Commit Type

Analyze changes → Select appropriate type:

  • New files added → feat
  • Bug fixed → fix
  • Refactoring → refactor
  • Documentation only → docs
  • Tests added → test
  • Build/config changes → chore

Step 3: Determine Scope

Use changed module/component as scope:

  • feat(auth): Authentication related
  • fix(api): API related
  • refactor(ui): UI related
  • No scope is also valid: chore: update dependencies

Step 4: Write Description

  • Under 72 characters
  • Use imperative mood (add, fix, update, remove...)
  • Lowercase first letter
  • No trailing period

Step 5: Execute Commit

Show the commit message and proceed immediately without asking for confirmation:

📝 Committing:

feat(orchestrator): add multi-CLI agent mapping support

- Add user-preferences.yaml for CLI configuration
- Update spawn-agent.sh to read agent-CLI mapping
- Update memory schema with CLI field

Co-Authored-By: First Fluke <our.first.fluke@gmail.com>
git add <specific-files>
git commit -m "<message>"

References

  • Configuration: config/commit-config.yaml
  • Guide: resources/conventional-commits.md

Important Notes

  • NEVER use git add -A or git add . without explicit permission
  • NEVER commit files that may contain secrets (.env, credentials, etc.)
  • ALWAYS use specific file names when staging
  • ALWAYS use HEREDOC for multi-line commit messages

FAQ

What does the oma-commit skill do?

Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.

How do I install oma-commit?

Run npx skills add https://github.com/gracefullight/stock-checker --skill oma-commit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/oma-commit/ (personal) or .claude/skills/oma-commit/ (project).

Which AI agents can use oma-commit?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is oma-commit safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains oma-commit?

It is published by gracefullight in gracefullight/stock-checker. It has 105 recorded installs.

More from gracefullight/stock-checker

View all →

stock-analysis

gracefullight/stock-checker

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management (create, add, remove assets), crypto analysis (Top 20 by market cap), and periodic performance reports (daily/weekly/monthly/quarterly/yearly). 8 analysis dimensions for stocks, 3 for crypto. Use for stock analysis, portfolio tracking, earnings reactions, or crypto monitoring.

Business & Finance12.1K installs

yahoo-finance

gracefullight/stock-checker

Get stock prices, quotes, fundamentals, earnings, options, dividends, and analyst ratings using Yahoo Finance. Uses yfinance library - no API key required.

Business & Finance4.7K installs

trading-analysis

gracefullight/stock-checker

Generate professional investment reports for stocks and ETFs. Use when user requests market analysis, investment reports, stock analysis, or trading recommendations for financial instruments (SPY, AAPL, TSLA, etc.). Creates institutional-grade reports with technical indicators, AI-powered insights, charts, and investment recommendations.

Business & Finance3.2K installs

backtesting-trading-strategies

gracefullight/stock-checker

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

financial data fetcher

gracefullight/stock-checker

Fetches real-time and historical market data, financial news, and fundamental data for trading decisions

Business & Finance539 installs

oma-debug

gracefullight/stock-checker

Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.