cp
The cp command automates the git workflow by running local reviews, staging changes while excluding generated or secret files, creating Conventional Commit messages with structured context blocks, committing those changes, pushing to the origin branch, and triggering remote CI checks before pull request creation. Use this when ready to finalize and submit work that has passed local linting, testing, and security validation.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.claude/commands/git/cp.md -o ~/.claude/commands/cp.mdcp.md
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.
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 working tree changes and create a Conventional Commit (no push).
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.