Loading...
Loading...
Found 14 Skills
Respond to PR review comments with critical evaluation. Use when addressing code review feedback, responding to bot review comments (Gemini Code Assist, CodeRabbit, etc.), or handling PR suggestions. Fetches comments, evaluates each against project context, applies valid fixes, declines invalid suggestions with reasoning, and posts responses.
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
Respond to online reviews. Use when: drafting replies for Google, Yelp, G2, or building review response templates.
Extract and respond to comments from a GitHub Pull Request. Use this skill when given a GitHub PR URL to review comments and act on the feedback, or when asked to address PR review feedback.
Manage customer reviews and developer responses using the `asc` CLI tool. Use this skill when: (1) Listing customer reviews for an app: "asc reviews list --app-id <id>" (2) Getting a specific review: "asc reviews get --review-id <id>" (3) Getting the response to a review: "asc review-responses get --review-id <id>" (4) Creating a response to a review: "asc review-responses create --review-id <id> --response-body <text>" (5) Deleting a response: "asc review-responses delete --response-id <id>" (6) User says "list reviews", "respond to review", "delete response", "check customer feedback", "reply to App Store review", or any customer review management task
Write point-by-point rebuttals to reviewer comments. Extract concerns from reviews, generate evidence-based responses, and format as a structured rebuttal document. Use after receiving peer review feedback.
App Store optimization skills for descriptions, screenshots, keywords, and review responses. Use when user needs help with App Store presence, ASO, or customer communication.
Respond to PR review feedback with maximum transparency. Analyze feedback, get second opinions on non-trivial decisions, post comments documenting every judgment, and implement fixes. All reasoning must be visible in PR comments. Keywords: PR review, code review response, review feedback, address comments, fix review.
Plan and write strategic rebuttals after real paper reviews arrive. Use this skill whenever the user has OpenReview reviews, reviewer comments, scores, confidence ratings, meta-reviews, author response windows, or wants to decide which experiments to run, infer reviewer intent, draft point-by-point responses, prepare follow-up discussion replies, or improve wording after reviews for ML/AI venues such as NeurIPS, ICML, ICLR, CVPR, ACL, EMNLP, or similar conferences.
Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review instead).
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely.