Pre-release QA review of a code change
Reviews a code change against its requirements and lists concrete defects by severity, each with a trigger scenario, fix and test. Use before merging or releasing.
730 reviewed prompts.
Reviews a code change against its requirements and lists concrete defects by severity, each with a trigger scenario, fix and test. Use before merging or releasing.
Designs a practical testing strategy for an application: risk map, test layers with targets, dependency handling, the first ten tests to write, CI gates and a four-week rollout. Use it when a suite is missing, slow or untrusted.
Splits a wedding budget across categories by your priorities, shows forgotten costs and savings options, schedules payments and sets what to cut first. Use it when planning or when quotes run high.
Checks the colors used across a product or design against a brand palette and proposes a consistent, accessible set. Use it when screens look uneven or after adding new colors.
Walks the path a new developer takes from finding your product to a first working result, finds the friction at each step, and prioritizes fixes to the product and the docs. Use before a launch or when developer sign-ups are not turning into usage.
Compares a built website or app against its design across browsers and screen sizes and returns a prioritized list of visual and interaction defects. Use it before launching a page or release.
Builds a practical test plan for an AI assistant or automated workflow: realistic test cases, pass/fail rules, metrics and review triggers. Use before rolling a workflow out to a team.
Recommends a suitable statistical approach for a question and dataset, explains it in plain language, lists assumptions to check and how to read the result. Use before analyzing survey, test or experiment data.
Turns commit messages or change lists into user-facing release notes, a short engineering note, and a rollout and risk summary. Use when preparing a release announcement.
Reviews a web page or component's code for accessibility, loading speed, layout stability, missing states and mobile behavior, then gives prioritized fixes with code. Use before shipping a page or when users report it is slow or hard to use.
Reads a code diff and its commit message and produces a plain summary of what changed, why it matters, and what a reviewer should check. Use before opening a pull request or when reviewing someone else's change.
Produces a grounded plan for a code change: affected files, two or three options with trade-offs, a recommendation, ordered steps, tests and risks. Use it before anyone starts writing code.