Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.
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 on a proposed plan, patch, or pull request.
Confirm the old and new resolved versions, source registry, checksums or lock data, release and migration notes, maintainer status, and reason for change. Flag renamed or transferred packages, install scripts, new binary downloads, new permissions, and large transitive-tree changes.
Search for changed APIs, defaults, configuration, data formats, network calls, and runtime requirements. Check production and development paths separately. Map each risk to a test, manual check, rollout signal, or unresolved gap.
Use ready for review, needs changes, or blocked on evidence. List findings by impact, with file or source evidence, owner, and required action. State whether rollback restores the old lock state and whether a data or config change makes rollback unsafe.
Do not approve, merge, deploy, or waive a check. A clean diff does not prove a safe runtime change.
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.