dependency-upgrade
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Use this when working on dependency-upgrade changes in this repository scaffold.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- HyperVon/agent-guidance-kittheir own version, first seen Nov 1, 2026
- navikt/copilottheir own version, first seen Nov 1, 2026
- agentkitco/agentkit-dev-skillstheir own version, first seen Nov 1, 2026
- Eliahhango/nullbyte-securitytheir own version, first seen Nov 1, 2026
- itsofficialadi/boundifftheir own version, first seen Oct 25, 2026
Used with
Projects with it also use incident-response, code-review and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillincident-response
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 6 projects that use this
- GoogleSkill
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
- +1 more from google
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- secondsky/sap-skills★ 462same name
- navikt/copilot★ 61same name
- xfstudio/skills★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- Eliahhango/nullbyte-security★ 4same name
- juanitourquiza/shipframe★ 4same name
- WST2002/claude-code-skills★ 4same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
- nafeeur/MaskShift★ 2same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bugfixSkill
- cli-toolSkill
- featureSkill
- library-packageSkill
- ops-changeSkill
- refactorSkill
- test-hardeningSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the matching checklist.
- Distinctive: line 24
Do not invent product-specific technology choices.
- Distinctive: line 25
Do not generate fake credentials or secrets.
- Very specific: line 26
Do not treat generated/cache/build output as source truth.
- Distinctive: line 36
Use stable validation names only.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dependency-upgrade
Read First
- AGENTS.md
- VALIDATION.md
- CHECKLIST.md
- .agents/context-map.md
Procedure
- Identify the source of truth.
- Read the matching checklist.
- Make the smallest change that preserves ownership boundaries.
- Validate with the stable validation names from VALIDATION.md.
Never
- Do not invent product-specific technology choices.
- Do not generate fake credentials or secrets.
- Do not treat generated/cache/build output as source truth.
Checklist
- Source of truth confirmed.
- Failure mode checklist reviewed.
- Validation plan stated.
Validation
Use stable validation names only. If a runner command is unconfigured, report it as skipped with reason.
Final Report
List files changed, validations run, validations skipped, skip reasons, and remaining risk.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.