claude-skills-reference/.claude/commands/git/cm.md at 4a6b514b06cbeaf0dab3205c80011322549ab2c0

firefrost-gaming/claude-skills-reference

Files

Reza Rezvani 4a6b514b06 feat(commands): add git workflow and quality gate slash commands

Implemented complete slash command system adapted from claude-code-skills-factory
for streamlined git workflow and quality assurance in claude-skills repository.

## New Slash Commands

### Git Workflow (3 commands)
- **git/cm.md** (/git:cm): Stage and commit (no push)
- **git/cp.md** (/git:cp): Stage, commit, and push with quality checks
- **git/pr.md** (/git:pr): Create pull request from current branch

### Quality Gates (2 commands)
- **review.md** (/review): Local quality checks (YAML lint, schema validation, Python syntax, markdown links)
- **security-scan.md** (/security-scan): Security validation (Gitleaks, Safety audit)

### Documentation
- **README.md**: Complete command reference with usage examples and workflows

## Key Features

✅ Step-by-step instructions for each command
✅ Safety checks (secrets detection, credential scanning)
✅ Conventional Commit format enforcement
✅ Integration with CI workflows (ci-quality-gate.yml)
✅ Quality gate enforcement before push

## Adaptations from Factory Project

- Updated directory paths for claude-skills structure
- Configured for repository-specific workflows
- Simplified for skills library workflow
- Removed factory-specific commands (build, validate-output, etc.)
- Kept essential git and quality commands only

## Usage

Commands available in Claude Code CLI:
- /git:cm - Commit without pushing
- /git:cp - Complete git workflow
- /git:pr - Create pull request
- /review - Run quality checks
- /security-scan - Run security validation

## Integration

Commands integrate with GitHub automation:
- /git:cp triggers ci-quality-gate workflow
- /git:pr triggers claude-code-review workflow
- Merged PRs trigger pr-issue-auto-close workflow

See .claude/commands/README.md for complete documentation.

2025-11-04 22:16:53 +01:00

919 B

Raw Blame History

description

description
Stage working tree changes and create a Conventional Commit (no push).

Run git status --short to review pending changes.
For each file, open a diff (git diff -- path/to/file) and ensure no secrets or credentials are present.
Stage the files intentionally (git add path/to/file). Avoid git add . unless every change was reviewed.
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.
Run git commit and paste the generated message + context from the template.
Show the resulting commit (git log -1 --stat) and keep the commit hash handy.
Do not push in this command. Use git/cp.md when you're ready to publish.

919 B Raw Blame History

919 B

Raw Blame History