Review outdated packages by support, change size, exposure, and value instead of treating every newer version as urgent.
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 to turn an update report into an ordered backlog.
For each direct dependency, record the installed version, newest compatible version, newest stable version, release date, support status, and source checked. Read the release notes and migration guide for candidate versions. Do not use a registry's latest tag as proof that an upgrade is safe.
Place each package in one group:
State the reason, likely change size, affected services, test owner, and next review date. Keep security findings linked to their advisory rather than copying severity into this review.
Do not recommend a major upgrade without reading its migration notes. Do not bundle unrelated upgrades merely to clear a dashboard. Never change version ranges or lockfiles until the user approves the plan.
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.