Orchestrate branch creation, PR staging, CI gating, and merge workflows.
npx skills add https://github.com/yanet-platform/yanet2 --skill ship-pr-yanet-platform
Please help me install this Agent Skill. Skill: ship-pr Source: https://github.com/yanet-platform/yanet2/tree/main/.claude/skills/ship-pr Command: npx skills add https://github.com/yanet-platform/yanet2 --skill ship-pr-yanet-platform
Land verified, reviewer-approved changes on main by enforcing a disciplined publish workflow: branch from origin/main, stage exactly the intended files, open a scoped PR, drive CI to green, address all review findings, and merge with the correct squash/rebase strategy before cleaning up branches and worktrees.
Open a scoped PR from a reviewer-approved change, drive CI to green, and complete the merge with the correct squash/rebase strategy.
High-intent search queries and answers about installing and using this skill.
Automating a git pull request workflow involves orchestrating branch creation, precise file staging, PR creation, CI gating, review remediation, and safe merge with branch cleanup. This ensures verified changes land on main through a disciplined publish workflow.
Managing stacked or parallel pull requests requires orchestrating multi-repo branch creation and CI gating while maintaining branch hygiene. Documented recovery procedures in references/branching-and-recovery.md provide clear guidance for resolving conflicts when they occur across parallel PR scenarios.
To ensure only intended files are staged before opening a pull request, you enforce precise file staging guardrails during the publish workflow. This prevents unintended changes from entering the scoped PR and keeps the review focused on specific modifications.
Yes, CI gating can block a pull request merge until tests pass. The publish workflow drives CI to green and enforces gated approvals before completing the merge with the correct squash or rebase strategy, ensuring only verified changes land on main.
To recover a git branch when conflicts occur during a pull request merge, follow documented recovery paths in references/branching-and-recovery.md. These procedures address conflict resolution for stacked or parallel PRs while maintaining branch hygiene and safe merge strategies.
Yes, this pull request workflow supports both squash and rebase merge strategies. It completes the merge using the correct strategy based on the scenario, followed by branch and worktree cleanup to maintain repository hygiene after landing verified changes.
sluongngAnalyze Bazel source, commit history, and GitHub context for cited explanations.
takemi-ohamaUpdate the main branch and delete the merged feature branch after a PR merge.
etylsarinEnforce feature-branch pull request workflows and prevent direct commits to main.
cosmixDesign and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.
