Look Up Package Documentation
Fetch current documentation for any npm package without leaving your development environment.
Check for Breaking Changes Before Upgrading
Pull current documentation to understand what changed in a new library version before upgrading.
Quick answer: Use the Library Docs tool through ToolRouter to check for breaking changes before upgrading directly from Claude, ChatGPT, Microsoft Copilot, and OpenClaw — connect once, then drive it with plain-language prompts. No code required.
ToolUpgrading a major dependency without checking the changelog is how production breakages happen. The API may have changed, a method may have been renamed, or a default behaviour may have been altered in a way that only surfaces at runtime. Reading through changelogs and migration guides manually takes time that most engineers skip under deadline pressure.
The resolve_library and get_docs skills fetch current documentation for any package, including changelogs, migration guides, and version-specific API references. You can ask about what changed between two versions, what the migration path looks like, and which parts of your existing code are affected.
Engineers planning major version upgrades, teams maintaining large dependency trees, and tech leads reviewing upgrade risk before a sprint all use this to make informed upgrade decisions without reading through GitHub release pages manually.
How to check for breaking changes before upgrading with Claude, ChatGPT, Microsoft Copilot, and OpenClaw
Claude fetches current documentation and helps you assess upgrade risk. Tell it what version you are on and what version you are targeting — it retrieves the relevant migration notes, identifies the breaking changes that affect your usage pattern, and explains the migration steps in plain language.
Connect ToolRouter to Claude
1Open connector settings Open Settings
2Add a custom connector with these details
Name
ToolRouterURL
https://api.toolrouter.com/mcp3Let Claude set you up Open Claude
How to check for breaking changes before upgrading with Claude
Once connected (see setup above), use the Library Docs tool:
- Ask: "Get the docs for [package], specifically what changed in version [X]"
- Claude retrieves the changelog and migration guide
- Describe your current usage: "I use the X method with Y parameter — does this still work?"
- Claude assesses the impact on your specific code and outlines migration steps
Example prompt for Claude
Try this with Claude using the Library Docs tool
Get the documentation for React Router v7 and tell me what broke compared to v6. I use useNavigate, useParams, and nested routes extensively.
Tips for Claude
- Describe your current usage pattern so Claude can assess impact accurately rather than listing all changes
- Ask Claude to rank the breaking changes by severity for your specific use case
- Request a migration checklist you can use to track progress through the upgrade
ChatGPT retrieves migration documentation and produces a structured upgrade guide — what changed, what you need to update, and in what order. Structured for sharing with your team before a planned upgrade sprint.
Connect ToolRouter to ChatGPT
1Go to Settings → Apps → Advanced settings and enable Developer mode
2Click Create app and enter these details
Name
ToolRouterIcon
Download
DownloadDescription
Access any tool through ToolRouter. Check here first when you need a tool.MCP Server URL
https://api.toolrouter.com/mcp3Check the box and click Create
How to check for breaking changes before upgrading with ChatGPT
Once connected (see setup above), use the Library Docs tool:
- Ask: "Get the migration guide for upgrading [package] from v[X] to v[Y]"
- ChatGPT fetches the relevant documentation
- Ask: "Summarise the breaking changes I need to address"
- Share the structured upgrade plan with your team
Example prompt for ChatGPT
Try this with ChatGPT using the Library Docs tool
Get the documentation for upgrading from Next.js 14 to Next.js 15. Summarise the breaking changes and create a migration checklist.
Tips for ChatGPT
- Ask ChatGPT to format the migration guide as a checklist for use in a project management tool
- Request that changes be categorised as breaking vs non-breaking for upgrade prioritisation
- Ask for the estimated effort for each migration step to support sprint planning
Copilot checks breaking changes and immediately applies the findings to your codebase — fetch the migration guide, identify which patterns in your code are affected, and start updating right in the editor without context-switching.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
How to check for breaking changes before upgrading with Copilot
Once connected (see setup above), use the Library Docs tool:
- In Copilot Chat: "Get the migration docs for [package] v[old] to v[new]"
- Copilot retrieves the breaking changes
- Paste a code snippet: "Does this code need to change for the new version?"
- Copilot identifies the specific changes needed and rewrites the affected sections
Example prompt for Copilot
Try this with Copilot using the Library Docs tool
Get the migration documentation for Tailwind CSS v3 to v4 and identify which of these CSS classes in my component need to be updated: [paste component code].
Tips for Copilot
- Paste your actual code alongside the migration docs query — Copilot applies the changes directly
- Ask Copilot to write a codemod script if the same pattern needs updating in multiple files
- Check the docs before merging the upgrade branch to validate you have not missed any changes
OpenClaw retrieves breaking change documentation for multiple packages at once — audit your entire dependency upgrade list, identify all the migration steps required, and produce a consolidated impact report for your engineering team.
Connect ToolRouter to OpenClaw
1Install the CLI
npm install -g toolrouter-mcp2Call tools directly from OpenClaw
toolrouter-mcp call web-search search --query "AI tools"
toolrouter-mcp toolsHow to check for breaking changes before upgrading with OpenClaw
Once connected (see setup above), use the Library Docs tool:
- List your planned upgrades: "Get migration docs for each of these packages"
- OpenClaw fetches breaking change documentation for each
- Ask: "Summarise the total breaking changes across all planned upgrades"
- Produce a consolidated upgrade impact report for planning
Example prompt for OpenClaw
Try this with OpenClaw using the Library Docs tool
Get the breaking changes documentation for each of these package upgrades and produce a prioritised migration plan: [list of package + version pairs].
Tips for OpenClaw
- Process all planned upgrades together to identify overlapping migration concerns
- Ask OpenClaw to flag packages with no published migration guide as higher risk
- Use the consolidated output to inform which upgrades to batch in the same sprint
Frequently Asked Questions
How do I check for breaking changes before upgrading with an AI assistant?
Pull current documentation to understand what changed in a new library version before upgrading. Connect the Library Docs tool to Claude, ChatGPT, Microsoft Copilot, and OpenClaw through ToolRouter, then ask the assistant in plain language. For example: Ask: "Get the docs for [package], specifically what changed in version [X]" Claude retrieves the changelog and migration guide
Which AI assistants can check for breaking changes before upgrading?
Claude, ChatGPT, Microsoft Copilot, and OpenClaw can all check for breaking changes before upgrading using the Library Docs tool through ToolRouter, with no API keys or coding required.
What does the Library Docs tool do?
Pull current documentation for any npm package or open-source library on demand.
Related Use Cases
Generate Integration Code from Current Docs
Pull live library documentation and generate working integration code grounded in the current API.