settle

Coordinate Volume PR stabilization through conflict resolution, CI checks, and merge-gate discipline.

2|Updated Oct 2, 2025

Search Tags:#automation #workflow #merge #code-review #ci #pull-request #settle

Ready to run

npx skills add https://github.com/misty-step/volume --skill settle-misty-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: settle
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/settle
Command: npx skills add https://github.com/misty-step/volume --skill settle-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Unblocks and cleans Volume PRs by coordinating fixes, CI gates, and reviews to achieve merge readiness.

Core Features & Use Cases

Phase 1: Fix — resolve conflicts, fix CI failures, and address review findings to unblock the PR.
Phase 2: Polish — perform hindsight architecture review, improve tests and docs, and reduce complexity where possible.
Phase 3: Refactor — targeted simplifications to lower overall complexity while preserving behavior.

Quick Start

Schedule and run the settle workflow to move a blocked PR toward merge readiness.

Frequently Asked Questions about settle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate resolving merge conflicts and fixing CI failures on pull requests?▼

To automate pull request stabilization, you can coordinate end-to-end fixes that resolve merge conflicts, address lint and typecheck failures, and pass CI checks for merge readiness without requiring admin bypass.

What is the best way to handle code review findings and unblock blocked PR branches?▼

Handling code review findings and unblocking blocked PR branches requires a structured workflow that addresses review comments, resolves branch conflicts, and enforces merge-gate discipline to achieve full merge readiness.

Does this PR merge automation workflow require GitHub CLI and jq?▼

Yes, this PR merge automation workflow requires both the GitHub CLI (gh) and jq as dependencies to query repository data, manage pull requests, and process JSON outputs during branch stabilization.

Can I use this workflow to refactor and polish code before merging cross-functional PRs?▼

Yes, you can use the workflow to perform Phase 2 polish including hindsight architecture review and test refinement, as well as Phase 3 targeted refactoring to lower complexity while preserving behavior across cross-functional teams.

Why do my automated PR fixes fail to pass CI checks without admin bypass?▼

Automated PR fixes must enforce merge-gate discipline by tracking evidence of changes and passing standard CI checks, rather than relying on admin bypass, to ensure true merge readiness and branch stability.