AgenticFor DevelopersCode Writing & Debugging

Dependency Audit & Upgrade Planner.

When starting a new project or doing a quarterly maintenance pass on an existing codebase.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1650 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
dependency-audit-upgrade-planner-4.md Β· 1650 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Code Writing & Debugging
- Use case: Dependency Audit & Upgrade Planner
- Source task:
  - I will provide my project's dependency file: {{paste_package_json_requirements_txt_pom_xml_go_mod}}. Audit it and:
  - 1. flag dependencies with known security vulnerabilities
  - 2. identify packages that are significantly out of date (major version behind)
  - 3. find unused or redundant dependencies
  - 4. flag dependencies with problematic licences for commercial use
  - 5. create a prioritised upgrade plan : what to update first and why, including breaking change risks

# Goal
A security/licence/version audit with a prioritised upgrade plan showing breaking change risks.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A security/licence/version audit with a prioritised upgrade plan showing breaking change risks.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledependency management expert
{{use_case}}Your specific valuedependency audit & upgrade planner
{{paste_package_json_requirements_txt_pom_xml_go_mod}}Paste package json requirements txt pom xml go modrequirements.txt

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When starting a new project or doing a quarterly maintenance pass on an existing codebase.

PRO TIP

Upgrade one dependency at a time and run your test suite after each β€” batch upgrades make it impossible to isolate what broke.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’