peter-commit-ops

What This Skill Does

peter-commit-ops serves as the critical bridge in your development workflow, transforming 'ready-to-submit' code changes into active, trackable pull requests. Instead of manually juggling git commands, this skill orchestrates a safe, atomic transition from your local workspace to the repository's CI/PR pipeline. It automates the verification of git status, handles branch management by ensuring feature branch usage, performs atomic commits with standardized messages, and pushes code to the remote repository while triggering PR creation via the GitHub CLI.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/chinasilva/peter-commit-ops

Use Cases

• Automated PR Lifecycle: When you want to transition from a code review to a merge request without manual overhead.
• Standardized Commit Hygiene: Ensures all commits adhere to conventional commit standards (feat/fix/chore) before reaching the remote server.
• Safety-First Deployment: Automatically checks for pre-commit linting or workflow requirements, preventing 'dirty' code from being pushed.
• Risk-Aware Pushing: Identifies and explicitly labels high-risk changes, ensuring that CI/PR gates are prioritized for sensitive modifications.

Example Prompts

1. "The code review passed and the changes look good, please go ahead and commit these, push to a new branch, and create a PR for me."
2. "I'm ready to ship the feature I've been working on. Can you handle the commit and create the pull request to the main branch?"
3. "Hey Peter, I've addressed the feedback from the last review. Please push these changes and start the PR process so we can move to CI."

Tips & Limitations

• Workplace Safety: The skill refuses to act if the workspace is empty or if previous review steps flagged the code as 'needs repair'.
• Strict Branching: It prevents you from committing directly to protected branches like 'main' or 'master' by forcing a feature branch creation.
• Selective Staging: It avoids the dangerous 'git add .' pattern by default, requiring specific file identification to ensure only relevant changes are included.
• CI Integration: While this skill initiates the PR, it expects subsequent tools like 'peter-ci-gate' to handle the final verification and merging process.