Commit code, create a pull request, and monitor CI status for merging.
npx skills add https://github.com/matthiaskloft/claude-skills --skill ship-matthiaskloft
Please help me install this Agent Skill. Skill: ship Source: https://github.com/matthiaskloft/claude-skills/tree/main/workflow-automation/skills/ship Command: npx skills add https://github.com/matthiaskloft/claude-skills --skill ship-matthiaskloft
This Skill automates the entire process of getting your completed code changes from your local machine into the main codebase, ensuring quality and smooth integration.
monitor-pr skill to track CI status and merge automatically upon success.Use the ship skill to commit, create a PR, and merge the current changes.
High-intent search queries and answers about installing and using this skill.
Automating git commit and pull request creation with CI monitoring involves staging changes, pushing with a descriptive message, opening a PR, and tracking continuous integration status for merging. This workflow requires git and gh CLI to handle version control and PR operations.
The best way to auto-merge a GitHub pull request after CI checks pass is to delegate to a monitoring process that tracks continuous integration status and merges automatically upon success. Post-merge cleanup ensures worktrees and branches are safely removed.
Yes, you need gh CLI installed to automate GitHub pull request workflows. The automation requires both git and gh CLI for version control and pull request operations, including generating PR titles, filling out templates, and handling CI status monitoring.
State tracking for CI/CD pull request automation works by persisting workflow execution details across sessions, ensuring robust recovery and continuous monitoring. This guarantees that the commit, PR creation, and CI status monitoring pipeline resumes correctly without losing progress.
Yes, automated pull request creation fills out existing PR templates. When generating a pull request, the workflow creates a title and body, and automatically populates available templates to ensure documentation standards are met before opening the pull request.
After an automated pull request merge, local branches and worktrees are automatically removed during post-merge cleanup. This ensures your environment stays clean and prevents obsolete worktrees or merged branches from accumulating.
AkallabetManage Git operations and GitHub interactions via the gh CLI.
sky770825Merge GitHub pull requests via squash with safety checks and branch cleanup.
jimmymalhanMerge pull requests automatically after CI checks pass.
tribedotrunCreate GitHub pull requests and trigger AI reviewers with CI monitoring.