skills.rest
sdcorejs
sdcorejsCOMMUNITY
Explore all skills by this author →
GitHub

sdcorejs-commit

Generate Conventional Commits messages with scope detection from staged file paths.

2|Updated Apr 18, 2026
Search Tags:#git#conventional commits#commit message#staged changes#secret scanning#scope detection#workflow safety
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdcorejs-commit
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-commit
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating consistent, machine-parseable Git commit messages while preventing unsafe or risky commit scenarios that can damage a shared codebase.

Core Features & Use Cases

  • Conventional Commits message generation: Produces a <type>(<scope>): <subject> message with scope auto-detected from staged paths.
  • Git safety pre-flight checks: Detects unsafe branches, empty diffs, potential secret leakage, mixed unrelated changes, and generated-files drift.
  • Bilingual output support (VI/EN): Generates instructions and guidance aligned with the change context.
  • Commit readiness guidance: Enforces correct staging behavior (explicit file paths) and verification after committing.

Quick Start

Use the sdcorejs-commit skill when you finish a cohesive change set and tell the AI to create the commit message for the staged work.

Frequently Asked Questions about sdcorejs-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commits messages automatically from staged changes?▼

To generate conventional commits messages, the Skill analyzes staged file paths to auto-detect scope and produces a standardized <type>(<scope>): <subject> format for machine-parseable changelogs.

What is the best way to prevent secret leakage and mixed concerns before a git commit?▼

The best way to prevent secret leakage and mixed concerns is running git pre-flight checks that scan staged diffs for potential secrets, empty diffs, and unrelated file changes before composing the commit.

How does automatic scope detection work for conventional commit messages?▼

Automatic scope detection works by parsing staged file paths in the repository to infer the affected component, then injecting that scope into the conventional commit message structure.

Can I use this conventional commit generator for a NestJS or Next.js repository?▼

Yes, you can use this conventional commit generator for NestJS and Next.js repositories, as it applies scope detection across multiple frameworks including angular-portal and sdcorejs-agent.

What happens if I have generated-files drift or an empty diff when creating a commit message?▼

If generated-files drift or an empty diff is detected, the commit process is halted by the pre-flight safety checks to prevent committing inconsistent or empty staged changes.

Why do I need explicit file paths staged for safe conventional commit generation?▼

You need explicit file paths staged to ensure commit readiness, as the Skill enforces correct staging behavior to verify staged and generated-files consistency before composing the final message.

Related Skills

Explore More Software Engineering Skills→
JoNaYeonJoNaYeon
1

work_git_commit-message

Analyze staged git diffs and generate Conventional Commits messages.

Community
Intermediate
NodeJSmithNodeJSmith
1

mine.commit-push

Stage changes, generate commit messages, update changelogs, and push to Git.

Community
Advanced
Women-Coding-CommunityWomen-Coding-Community
10

commit

Stage, review, and commit git changes with sensitive data detection.

Official
Advanced
RaNDoM6913RaNDoM6913
1

commit-helper

Analyze code changes to generate conventional commit messages with secret detection.

Community
Intermediate