push

Automated code validation runs compile, lint, and test scripts before pushing changes to ensure code quality. This process catches errors early by executing necessary checks locally, preventing broken code from entering your continuous integration workflows.

Yes, you need the gh CLI installed to create pull requests from the command line. This Skill requires both git and gh CLI for GitHub operations, using them to manage branches, push updates, and handle PR creation or updates automatically.

Handling non-fast-forward errors requires clear recovery steps when a push fails due to branch conflicts. This Skill provides built-in error handling that identifies common issues like non-fast-forward pushes or authentication errors and outputs actionable recovery instructions.

Yes, you can update an existing pull request instead of creating a new one. Branch management logic detects the current branch state and handles the push accordingly, automatically creating a new PR or updating an existing one to streamline your workflow.

Running CI/CD checks locally before creating a GitHub pull request ensures code quality and readiness for review. Automated validation executes necessary scripts to compile, lint, and test your code, reducing manual steps and preventing deployment failures.