Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.
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 after an upgrade plan has a reviewed target.
Update the manifest and lockfile with the package manager. Make only the code or configuration edits required by the verified migration notes. Do not mix formatting, refactors, unrelated package bumps, or silent alert suppressions into the change.
Run the smallest relevant tests first, then the project checks required by its contribution guide. Inspect the resolved dependency tree and built artifact. For a security fix, rerun the scanner or version check that found it. Record commands, results, and anything you could not run.
State the old and new versions, reason, advisory or release-note sources, behaviour changed, files changed, test evidence, known risk, rollout check, and rollback. Mark it draft when approval or a check remains.
Never merge, deploy, bypass a failed check, or claim production is fixed. Hand the draft and evidence to the named reviewer.
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.