monitor-pr

To automate pull request monitoring, the Skill continuously checks CI status every 4 minutes, attempts automated fixes for simple failures or review comments, and merges the PR once all checks pass and reviews are approved.

Yes, you can resume monitoring a GitHub Actions workflow across sessions. The Skill persists its tracking state locally using a `.workflow-state.json` file, allowing the automated CI monitoring and merging process to resume seamlessly.

Automated PR fixing works by detecting failing CI checks and simple review comments, then attempting automated fixes directly on the branch. It iterates through these fixes while continuously monitoring the status every 4 minutes before merging.

Limitations of automating PR merges include pre-flight checks that validate branch name safety and prevent duplicate monitors from running. It also relies on automated fixes for simple failures, meaning complex CI errors or deep review threads may require manual intervention.

You do not need explicit GitHub Actions configurations to use this monitoring. The Skill operates by checking the CI status of your existing GitHub Pull Request workflow and handling the merging process independently through its own background monitoring loop.

The best way to handle pull request state persistence for cross-session CI monitoring is using a local `.workflow-state.json` file. This approach stores the monitoring context, allowing the automated checks and merge attempts to resume after interruptions.