cm
The cm command stages git working tree changes with deliberate file review and creates a Conventional Commit message without pushing. Use this command when preparing changes for version control, ensuring each modification is inspected for secrets before committing with standardized formatting that includes scope and type prefixes.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.claude/commands/git/cm.md -o ~/.claude/commands/cm.mdcm.md
1. Run `git status --short` to review pending changes. 2. For each file, open a diff (`git diff -- path/to/file`) and ensure no secrets or credentials are present. 3. Stage the files intentionally (`git add path/to/file`). Avoid `git add .` unless every change was reviewed. 4. Generate a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert). - Commit subject ≤ 72 chars. - Scope uses kebab-case (e.g., `feat(marketing-skill): ...`). - Use `.github/commit-template.txt` for Context / Testing / Reviewers sections. 5. Run `git commit` and paste the generated message + context from the template. 6. Show the resulting commit (`git log -1 --stat`) and keep the commit hash handy. 7. **Do not push** in this command. Use `git/cp.md` when you're ready to publish.
Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Stage, commit, and push the current branch following git governance rules.
Create a pull request from the current branch.
Run the full 8-phase plugin audit pipeline on a skill directory.
Run the local review gate before pushing.
Run the security scan gate before pushing.
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.