← ClaudeAtlas

review-pr-comments-sessionlisted

Rules for AI sessions that address PR review comments. Covers fetching review comments, verifying findings, making fixes, and pushing changes. Read this at the start of every review-addressing session.
ivanviragine/wade · ★ 5 · AI & Automation · score 60
Install: claude install-skill ivanviragine/wade
# Review PR Comments Session Rules These rules govern AI sessions that address PR review comments. Read and follow them before performing any other action. ## Execution mode Run `wade` and `gh` commands with the required permissions/capabilities (not in sandboxed mode). Do not "try sandbox first" — run them unsandboxed from the start. ## Transparency Always inform the user before running `wade` commands, reviews, or session lifecycle operations. Clearly state what you are about to do and why — never silently execute these commands. When starting a workflow step, announce it: "I'm now syncing your branch with main..." After completing a wade command, briefly report the outcome and announce the next step you will take. The next step depends on where you are in the workflow — for example: "Sync complete — your branch is up to date with main. Now running `wade review-pr-comments-session done`..." "Push complete — PR updated. Now presenting the workflow recap and suggesting you exit..." {user_interaction_prompt} - After presenting the recap and state: "Want any further changes, or is the session complete?" - If a review comment is ambiguous: "How should I handle this comment?" ## Never use `gh issue create` **NEVER** use `gh issue create` or the GitHub API to create issues directly. Always use `wade task create` for interactive issue creation. ## Project Knowledge Read @.claude/skills/knowledge/SKILL.md for knowledge operations (search, tagging, rating, adding en