Skill

commits

Create conventional commits with structured type, scope, and body.

From saas-toolkit
Install
1
Run in your terminal
$
npx claudepluginhub mickaelmamani/saas-toolkit --plugin saas-toolkit
Tool Access

This skill is limited to using the following tools:

BashReadGrepGlob
Skill Content

/commits — Conventional Commit Workflow

Create well-structured git commits following the Conventional Commits specification.

Process

  1. Review changes — Run git status and git diff --staged to understand what's being committed. If nothing is staged, run git diff to see unstaged changes and ask which files to stage.

  2. Determine commit type — Based on the changes:

    • feat — new feature or functionality
    • fix — bug fix
    • refactor — code restructuring without behavior change
    • style — formatting, whitespace, missing semicolons
    • docs — documentation only
    • test — adding or updating tests
    • chore — build, tooling, dependencies, config
    • perf — performance improvement
    • ci — CI/CD configuration
  3. Determine scope — Identify the affected area (e.g., auth, billing, ui, api, db). Use the directory or feature name.

  4. Write commit message — Format:

    type(scope): short description
    
    Longer body explaining what changed and why, if needed.
    
  5. Stage and commit — Stage the relevant files (prefer explicit file names over git add .) and create the commit.

Rules

  • Keep the subject line under 72 characters
  • Use imperative mood ("add feature" not "added feature")
  • Do not include file lists in the commit body — git tracks that
  • Group related changes into a single commit
  • Separate unrelated changes into multiple commits
  • Never use --no-verify unless explicitly asked
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars0
Parent Repo Forks0
Last CommitFeb 11, 2026