pr-sweep

Solid

Review every open PR, apply the review findings, and merge each one once CI is green.

AI & Automation 16 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# PR sweep Take every open PR from review to merge without asking between steps. With PR numbers, sweep only those. With `--no-merge`, stop at green PRs. ## 1. List ```bash gh pr list --state open --json number,title,headRefName,additions,deletions,author ``` Skip PRs by other authors and drafts; report them. Empty list: stop. ## 2. Review Use the `code-reviewer` agent for Go diffs when available. Review other diffs against the project rules. Independent reviews may run in parallel; read every result before editing. ## 3. Verify each finding A finding is a claim, not a task. Before acting on one: - Reopen the file and line it cites on the PR head. - Reproduce behavior claims with a built binary or a failing test. - Check vendor claims against the vendor page, not memory. Keep what holds. Record what does not, with the reason. ## 4. Apply Check out the PR branch in the main checkout (worktree agents cannot run git while the RTK hook rewrites it) and pull. For each confirmed finding: - Fix it on the branch. Test first for behavior changes: the new test must fail on the old code. - A finding that needs a different design or touches other targets gets its own issue (`gh issue create --assignee Chemaclass` with a label). Do not widen the PR. - A finding you reject after verification is answered, not ignored. Then post one PR comment listing the commit that applied the findings, the issues filed, and each rejection with its reason. ## 5. Gate Before every push, all ...

Details

Author
Chemaclass
Repository
Chemaclass/agnostic-ai
Created
4 months ago
Last Updated
today
Language
Go
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category