Skip to content
cccskills
FreePublished on GitHub

dependency-upgrade-plan

Plan a small, testable dependency upgrade with compatibility checks, owners, rollout evidence, and rollback steps.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Dependency upgrade plan

Use this once the current and target versions are known.

Read before planning

Check release notes, migration guides, support policy, known regressions, and the project's use of changed APIs or configuration. Name every source and the versions it covers. Search the repository for removed or changed features.

Write the plan

Include:

  1. Reason and evidence for the target version.
  2. Files and services likely to change.
  3. Required code, config, schema, or build edits.
  4. Tests to add or run, tied to the affected behaviour.
  5. Build and scanner checks.
  6. Rollout owner, observation window, and stop conditions.
  7. Exact rollback route.

Split major, framework, runtime, and unrelated security upgrades when they can be tested alone. Mark assumptions and missing test coverage.

Approval line

The plan may propose a branch or pull request. It does not authorise a merge, deploy, data migration, risk acceptance, or production change.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill