dependency-update Skill
Guide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries. Published by microsoft in haste.
Decision snapshot
Is this a fit?
Testing, Security review, Design and media, Includes SKILL.md
Compatibility not yet detected.
Shell access
Copy skill directory
2 months ago · MIT license
Access note: Shell access.
What is dependency-update Skill?
Guide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries. Published by microsoft in haste. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Security review
- Design and media
- Testing use cases
- Security review use cases
Declared skill metadata
- Source file: .github/skills/dependency-update/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use dependency-update Skill
- Use it for testing.
- Use it for security review.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/haste
- Skill file: .github/skills/dependency-update/SKILL.md
What it does
Guide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries.
Skill instructions
Dependency Update Overview A structured process for safely updating project dependencies. Updates are categorized by risk level and applied in controlled batches with verification at each step. Key Concepts Semantic Versioning Risk Tiers - Patch (x.x.X): Bug fixes only. Safe to batch. - Minor (x.X.0): New features, backward compatible. Update in small batches. - Major (X.0.0): Breaking changes. Update one at a time. Read the changelog. Patterns & Techniques Safe Update Process Step 1: Audit bash Python pip list --outdated JavaScript npm outdated Step 2: Categorize — Group by risk tier (patch, minor, major). Step 3: Update per batch 1. Update the dependency 2. cd hastelib && hatch build -t wheel — check build 3. cd hastelib && hatch run test:pytest — check behavior 4. cd ui && npm run lint — check for new warnings 5. If tests fail, investigate and fix or revert Step 4: Security check — Scan for known vulnerabilities. Step 5: Commit — One commit per logical group: chore(deps): update [pa
Verified compatibility and discovery
Frequently asked questions
What is dependency-update?
dependency-update is a open-source AI agent skill with Copy skill directory. Guide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries.
Who is dependency-update best for?
dependency-update is best for reusing agent instructions, scripts, and references, testing workflows, security review workflows, design and media workflows.
How do I install dependency-update?
Install or run dependency-update using Copy skill directory. Check dependency-update for the latest setup command.
Is dependency-update actively maintained?
dependency-update may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
