Files
claude-skills-reference/.claude/commands/git/cp.md
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

910 B

description
description
Stage, commit, and push the current branch following git governance rules.
  1. Run /review to ensure lint/tests/security checks pass locally.
  2. Review and stage changes with git add (avoid staging generated or secret files).
  3. Craft a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
    • Use .github/commit-template.txt and include Context / Testing / Reviewers blocks.
    • Never add AI attribution strings to commits.
  4. Commit with git commit using the prepared message. If commitlint fails, fix the message and retry.
  5. Push to origin: git push origin $(git branch --show-current).
  6. Trigger remote checks for visibility:
    • gh workflow run ci-quality-gate.yml --ref $(git branch --show-current)
  7. Wait for workflow to finish (gh run watch --workflow ci-quality-gate.yml) before opening a pull request.