agent-skills

Use when running a critical, skeptical pass over a GitHub pull request — either as the author before requesting human review, or as a reviewer wanting a structured first cut — produces a findings report grouped by severity (High / Medium / Low / Done well) and, after confirmation, posts it as a single comment on the PR. Not for inline line-by-line comments (pr-review), an interactive walkthrough (guided-review), or your own branch before it has a PR (self-review).

Author a new agent skill or improve an existing one in this plugin - write the SKILL.md frontmatter and description, structure the body, split references, and fix skills that under- or over-trigger. Use when asked to create/write a skill, make a SKILL.md, improve/refactor a skill, or fix a skill's description.

Use when you want to understand and review a GitHub pull request as a reasoning companion rather than an automated reviewer. Phase 1 explains the PR's goal and purpose concisely with a concrete example, then gates on your confirmation before Phase 2 does a thorough code review that surfaces genuine issues, not nitpicks. Read-only — never posts anything to the PR; you post any feedback yourself. This is the default for "review this PR" / "walk me through this PR" requests; when the goal is to post comments, use pr-review or adversarial-review explicitly instead. Not for your own branch before it has a PR (self-review).

Find source lines and expressions no test asserts on via mutation testing (line-removal by default, Stryker on request), then close each gap with a test that fails when the code is broken. Scopes to a file, a package, or the branch diff, and estimates runtime before mutating.

Write or rewrite the description of a Vaadin pull request from the branch diff — fills the repo PR template as short, bullet-driven markdown with a "How to test" section. Use when asked to write a PR description, fill in the PR template, describe this branch for a PR, update or improve the PR body, or add a how-to-test section. Drafts in chat and only updates the PR after explicit confirmation. Not for reviewing a PR (guided-review, adversarial-review, pr-review) or for reviewing your own branch before opening it (self-review).

Review a GitHub pull request with the plugin's reviewer agents and, after confirmation, post the findings as inline Conventional Comments (issue / suggestion / question / nitpick, blocking or non-blocking). Use when asked to review a PR and leave line comments, do a full review of a pull request, or post review findings on a PR. Not for a single summary comment (adversarial-review), a walkthrough that never posts (guided-review), or your own branch before it has a PR (self-review).

Plan and run a structural refactor of web component sources without a behavior change. Use when asked to refactor a component, a mixin or a package, to remove duplication between sibling components, to extract a controller or consolidate shared logic, to simplify a mixin that grew too large, or to order several refactors. Not for a review of a branch or a pull request, which is self-review, guided-review or pr-review. Not for finding test gaps, which is mutation-coverage. Not for a cleanup inside an uncommitted diff, which is simplify.