agentsclimarketplace
Sign in

Deprecation triage

Skill vergil-project/vergil-claude-plugin/skills/deprecation-triage

Triage a deprecation warning into a tracked decision. Use whenever a deprecation warning surfaces — the detect-deprecation-warnings PostToolUse hook fires, or the human points at a warning in test/CI/build output and asks how to handle it ("triage this deprecation", "what do we do about this warning"). Searches for an existing issue, decides defer-or-fix, and applies issue-tracking and suppression rules consistently.From its SKILL.md

Install
npx -y skills add vergil-project/vergil-claude-plugin --skill deprecation-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, as published. Nobody here has run it

Deprecation triage

Table of Contents

Overview

Apply the deprecation warning triage policy to prevent warning drift and ensure issues are tracked and resolved in-cycle or deferred explicitly.

When to use

The primary trigger is the detect-deprecation-warnings PostToolUse hook (hooks/scripts/detect-deprecation-warnings.sh). After any test command (pytest, cargo test, go test, etc.), the hook scans output for deprecation-warning patterns. When it finds one, it injects context telling the agent to invoke this skill after completing the current task.

The skill can also be invoked directly via /vergil-tooling:deprecation-triage when a deprecation warning surfaces outside the hook's scope (manual testing, log review, dependency changelog reading, etc.).

Inputs

Collect or request:

  • Full warning text
  • Location (file/module and call site)
  • Environment (dev/test/prod)
  • First seen date and version
  • Whether the warning is user-visible

Workflow

  1. Search for an existing issue that matches the warning text and location.
  2. If an issue exists and the warning is mid-cycle, defer to the next dependency update.
  3. If no issue exists, create one using the template below.
  4. Attempt a code-only fix if no dependency upgrade is required.
  5. If a dependency upgrade is required, defer to the start-of-cycle upgrade.
  6. If user-visible and deferred, suppress and document the suppression.
  7. Update the issue with each re-test and close when resolved.

Identity check (step 3). Creating issues requires write access. If the acting identity (USER / AUDIT) cannot create the issue, prepare the title and body and hand them to the human to create — do not fail silently.

Issue template

Title: Deprecation: <dependency or component> - <short description>

Warning text:
<full warning message>

Location:
- file/module:
- call site:
- environment (dev/test/prod):

Reproduction:
- minimal command or steps:
- notes on reproducibility:

First seen:
- date:
- version:

Impact assessment:
- user-visible: yes/no
- behavior risk:

Attempted fixes:
- code changes tried:
- result:

Upgrade assessment:
- required dependency version:
- upgrade scope:

Decision:
- fix now / defer to next cycle
- rationale:

Suppression (if any):
- suppression method:
- removal criteria:

Resources

  • docs/development/deprecation-warnings.md

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.