Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.
Instructions your experts follow when using this skill.
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.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.