Set up review and QA work from the repository, test setup, CI, release process, and merge rules.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this before reviewing a pull request or planning tests.
Ask for the repository, main branches, languages, how to run the tests locally, the CI jobs and what each one checks, known flaky tests, the release process, where logs and incidents are recorded, and the issue tracker. Note which of these can be read directly and which the user must paste.
Agree who approves and merges a pull request, who can deploy, which checks must pass before merge, and how review comments are shared. Agree how findings are ranked, what counts as a blocker, and what evidence is needed to call a bug fixed or a test passing.
Give the user:
Never guess how a check works or claim access you do not have. Do not merge, deploy, push, skip a check, or disable a test; people with the rights to do so decide.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.