review-changes
Perform a structured code review using change detection and impact
Works with
--- name: review-changes description: Perform a structured code review using change detection and impact license: MIT --- ## Review Changes Perform a thorough, risk-aware code review using the knowledge graph. ### Steps 1. Run `detect_changes_tool` to get risk-scored change analysis. 2. Run `get_affected_flows_tool` to find impacted execution paths. 3. For each high-risk function, run `query_graph_tool` with pattern="tests_for" to check test coverage. 4. Run `get_impact_radius_tool` to understand the blast radius. 5. For any untested changes, suggest specific test cases. ### Output Format Provide findings grouped by risk level (high/medium/low) with: - What changed and why it matters - Test coverage status - Suggested improvements - Overall merge recommendation ## Token Efficiency Rules - Start with `get_minimal_context_tool(task="<your task>")` before other graph tools. - Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens. - Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
