Nm Sanctum Commit Messages

Generate conventional commit messages from staged changes with correct type/scope

Security Scan

Instructions and requirements match the stated purpose: the skill only reads staged Git diffs, drafts a conventional commit message, and writes a local preview file; it requests no extra credentials or installs.

Purpose & Capability

Name/description claim to generate conventional commit messages from staged changes. The SKILL.md only references git commands, optional use of a 'sem' tool if present, and writing a local preview file — all directly related to that purpose.

Instruction Scope

Instructions tell the agent to run git status/diff/log on the repository and to write ./commit_msg.txt. This is expected, but it means the agent will read repository contents (staged hunks and recent commits). The SKILL.md also optionally invokes an external tool 'sem' when available; that tool is not required and is clearly optional.

Install Mechanism

No install spec or code files — instruction-only skill. Nothing is downloaded or written to disk by an installer. Lowest-risk install posture.

Credentials

No environment variables, credentials, or config paths are requested. The only required privileges are read access to the local Git repository and permission to create ./commit_msg.txt, which are proportional to the stated task.

Persistence & Privilege

always:false and default invocation settings. The skill writes a single local preview file and does not request persistent system-wide changes or modify other skills. No elevated privileges requested.

Assessment

This skill appears coherent and limited to generating commit messages from staged changes. Before using it, confirm you are comfortable letting the agent read your staged diffs and recent commit history (these may contain sensitive data). The skill writes a local file ./commit_msg.txt — review that file before running git commit. If you enable the optional 'sem' integration, ensure the sem binary is from a trusted source. As a best practice, run the skill in a trusted repo and inspect the generated message before committing.

Night Market Skill — ported from claude-night-market/sanctum. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Conventional Commit Workflow

When To Use

• Generating conventional commit messages from staged changes

When NOT To Use

• Full PR preparation: use sanctum:pr-prep
• Amending existing commits: use git directly

Steps

1. Gather context (run in parallel):

   • git status -sb
   • git diff --cached --stat
   • git diff --cached
   • git log --oneline -5
   • When sem is available (see leyline:sem-integration): sem diff --staged --json for entity-level changes

   If nothing is staged, tell the user and stop.

   When sem output is available, use entity names (function, class, method) in the commit subject and body instead of parsing raw diff hunks. For example, "add function validate_webhook_url" instead of "add validation logic to notify.py".

2. Classify: Pick type (feat, fix, docs, refactor, test, chore, style, perf, ci) and optional scope.

3. Draft the message:

   • Subject: <type>(<scope>): <imperative summary> (50 chars max)
   • Body: What and why, wrapped at 72 chars
   • Footer: BREAKING CHANGE or issue refs

4. Slop check: reject these words and replace with plain alternatives:

   Reject	Use instead
   leverage, utilize	use
   seamless	smooth
   comprehensive	complete
   robust	solid
   facilitate	enable
   streamline	simplify
   optimize	improve
   delve	explore
   multifaceted	varied
   pivotal	key
   intricate	detailed

   Also reject: "it's worth noting", "at its core", "in essence", "a testament to"

5. Write to ./commit_msg.txt and preview.

Rules

• NEVER use git commit --no-verify or -n
• Write for humans, not to impress
• If pre-commit hooks fail, fix the issues