AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ruby Commit Message

skill-zarpay-rails-template-ruby-commit-message · by zarpay

Use when committing code changes in Ruby or Ruby on Rails projects — guides commit message structure, type selection, and body content following Conventional Commits format

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-zarpay-rails-template-ruby-commit-message

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ruby Commit Message? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Ruby Commit Message

Overview

Write structured commit messages following Conventional Commits. The body should help a junior Ruby on Rails developer understand the change during a debugging session.

Format

():

Quick Reference — Commit Types

| Type | Purpose | |------|---------| | feat | New feature | | fix | Bug fix | | refactor | Refactoring (no behavior change) | | perf | Performance improvement | | docs | Documentation only | | test | Test additions or corrections | | build | Build system or dependencies | | ci | CI configuration | | chore | Maintenance tasks | | style | Code formatting (no logic change) | | revert | Revert previous commit | | meta | Repository metadata | | license | License changes |

Subject Line Rules

  • Imperative mood: "Add", "Fix", "Update", "Remove"
  • Present tense: "Add feature" not "Added feature"
  • Capitalized first letter, no period at end
  • Maximum 70 characters
  • Scope (optional): noun describing the section of codebase, e.g. (api), (auth)

Body Guidelines

Couple of sentences, wrapped at 72 chars, blank line after subject. Write for a junior Ruby developer: simple language they can understand during debugging. Add any useful information that would help a junior Ruby developer understand the impact of the change, why the change was done.

  • WHY — motivation, problem, or user impact. Use context if it exists for this.
  • WHAT changed — make this brief; the diff already shows the HOW
  • HOW — only when there are details about the how that are not reflected by the code or the naming in the code

Call out tradeoffs when supported by context. Do not invent details.

Footer & AI Attribution

Fixes TICKET-123       # or: Fixes #123, Refs TICKET-123
BREAKING CHANGE: ...   # for breaking changes; use ! in type too: feat(api)!:
Co-Authored-By:     # when AI generated the change

Do NOT add "Generated by AI" or "Written with Claude" in the subject or body. Use only Co-Authored-By.

Examples

Security/Authorization Fix

fix(api): Scope report access to current user

Report.find allowed any authenticated user to view any report by ID.
Querying through current_user.reports makes Rails raise RecordNotFound
(404) if the report doesn't belong to the requester.

New Feature

feat(alerts): Add Slack thread replies for alert updates

When an alert is updated or resolved, post a reply to the original
Slack thread. This keeps related notifications grouped together.

Refs GH-1234

Breaking Change

feat(api)!: Remove deprecated v1 endpoints

Remove all v1 API endpoints deprecated in version 23.1.
Clients should migrate to v2 endpoints.

BREAKING CHANGE: v1 endpoints no longer available

Common Mistakes

| Mistake | Fix | |---------|-----| | Body explains HOW without context | Only include HOW when it helps debugging | | Subject describes implementation ("Changed X to Y") | Use imperative: "Fix X", "Add Y" | | Body repeats what the diff shows | Explain WHY it was changed | | Subject over 70 characters | Trim scope or rephrase | | "Generated by AI" in body | Use Co-Authored-By footer only |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills