← ClaudeAtlas

create-prlisted

Open or update a pull request and handle in-scope CI failures. Use when the user wants to prepare a PR. For matching managed tasks, finalize the task as ready to merge; stop only when the current head is CI-green, and never merge or invoke sync-main.
SrdjanCoric/skills · ★ 18 · AI & Automation · score 67
Install: claude install-skill SrdjanCoric/skills
# Create Pull Request Commit the current unit of work, push its branch, open or update its PR, and wait for CI. Stop when the current PR head is ready to merge. Do not merge the PR or invoke `sync-main`. ## Inputs Accept an optional feature name, an optional managed task path, and optional evidence from `finish-task`: - task-review and review-fix-worker outcome (fixed findings, skipped minors with reasons); - automated and manual verification proof; - accepted security risks and the user's reasons. A managed task path authorizes the `[~]` to `[>]` transition described below. Without a supplied path, treat a unique active task whose `**Branch**` matches the current branch as managed. Do not guess when more than one task matches. ## Process ### 1. Gather current state Run: ```sh git branch --show-current git status --short git diff --cached --stat git diff --stat git log main..HEAD --oneline || git log origin/main..HEAD --oneline git diff --name-status main...HEAD || git diff --name-status origin/main...HEAD git diff --stat main...HEAD || git diff --stat origin/main...HEAD ``` Confirm the current branch is not `main`. Identify the observable result, dependencies, and material risks in the diff. Inspect the base, current head, staged state, and working tree, then classify the complete change as `plan-only`, `documentation-only`, `dependencies`, `configuration`, `code`, or `mixed`. Derive the matching validation tier and retain both decisions in working context. Fail cl