Conduct comprehensive PR reviews with sprint/roadmap context awareness. Invoke when user says "review PR", "check this PR", "review pull request
Conducts comprehensive PR reviews with sprint and roadmap context awareness. Activates when user requests a PR review to provide feedback that considers project goals and avoids suggesting work already planned in the backlog.
/plugin marketplace add fusupo/escapement/plugin install escapement@fusupo-escapementThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Conduct thorough, context-aware pull request reviews that consider the full project roadmap, sprint context, and epic hierarchy. This skill avoids suggesting improvements already planned in the backlog and focuses feedback on the specific scope of the PR.
This skill activates when the user says things like:
Execute these in parallel:
PR Details:
mcp__github__get_pull_request(owner, repo, pullNumber)
mcp__github__get_pull_request_diff(owner, repo, pullNumber)
mcp__github__get_pull_request_files(owner, repo, pullNumber)
mcp__github__get_pull_request_comments(owner, repo, pullNumber)
Project Context:
CLAUDE.md for architecture and prioritiesIdentify Closing Issue(s):
Parent Issue Discovery:
Sibling Issues:
Dependency Mapping:
Current Sprint:
Roadmap Position:
Remaining Work:
Planned Improvements:
Execute each perspective while avoiding suggestions already planned:
Focus: Does this advance project capabilities toward stated goals?
Output: Assess business value within larger context. Skip suggestions already in sibling issues.
Focus: Code quality appropriate for current velocity.
Output: Review technical correctness within larger plan. Skip suggestions covered by planned tech debt issues.
Focus: How this piece fits with related work.
Output: Evaluate coordination with planned work. Focus on enabling upcoming issues.
Focus: Appropriate quality for current epic phase.
Output: Assess quality within sprint context. Defer suggestions scheduled for later.
Focus: Preparing for future work.
Output: Evaluate within full roadmap. Highlight dependencies and coordination.
Review Structure:
## PR Review: #{pr_number} - {title}
### Context
- **Issue:** #{issue_number} - {issue_title}
- **Epic:** {parent epic if exists}
- **Sprint:** {current sprint/milestone}
### Summary
{Brief assessment of PR's contribution to project goals}
### Product Assessment
{Does this deliver intended value?}
{How does it advance the epic/project?}
### Technical Review
{Code quality observations}
{Architectural alignment}
{Integration considerations}
### Suggestions
{Only suggestions NOT already in backlog}
{Focus on this specific PR scope}
### Questions
{Clarifying questions if any}
### Verdict
{APPROVE / REQUEST_CHANGES / COMMENT}
{Summary of required changes if any}
---
**Context Awareness:**
- Reviewed against {N} related issues in epic
- Checked {M} planned improvements in backlog
- Aligned with sprint goals: {yes/no}
After generating the review, confirm with the user before submitting:
AskUserQuestion:
question: "Submit this review to GitHub?"
header: "Review"
options:
- label: "Submit as APPROVE"
description: "Approve the PR with this review"
- label: "Submit as REQUEST_CHANGES"
description: "Request changes before approval"
- label: "Submit as COMMENT"
description: "Add review as comment without approval decision"
- label: "Edit review first"
description: "I want to modify the review before submitting"
- label: "Don't submit"
description: "Keep review local, don't post to GitHub"
If user chooses to submit:
mcp__github__create_and_submit_pull_request_review(
owner, repo, pullNumber,
body: "{review content}",
event: "APPROVE" | "REQUEST_CHANGES" | "COMMENT"
)
❌ Could not find PR #{number}
Verify the PR number and repository.
⚠️ PR has no linked issue.
Review will proceed without epic/sprint context.
⚠️ This PR has {N} files changed.
Consider breaking into smaller PRs for easier review.
Reviews output from:
create-pr skill - Reviews PRs created by the workflowReads context from:
Version: 1.1.0 Last Updated: 2025-12-31 Maintained By: Escapement Changelog:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.