kubebar

Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.

Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.

Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.

Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.

Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.

Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.

Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture.

Use when a GitHub issue backlog needs read-only classification, prioritization, duplicate spotting, or clarification gaps called out.

Use when open pull requests need a read-only dashboard showing review state, scope, blockers, conflicts, and merge readiness.