Update Project Dependencies
Developmentupdate-project-dependenciesUpdate Project Dependencies is an Agent Skill for development published in the chattocorp/chatto repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use this if you want to update all project dependencies while respecting semver compatibility.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/chattocorp/chatto/blob/HEAD/.agents/skills/update-project-dependencies/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-project-dependencies, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Update Project Dependencies
This skill updates all project dependencies while respecting semver compatibility, then runs tests to verify everything still works.
Instructions
Follow these steps in order:
1. Capture Current State
Before making any changes, read and save the current dependency versions:
- Read
cli/go.mod- note the versions of direct dependencies (therequireblocks without// indirect) - Read
frontend/package.json- note the versions indevDependencies
2. Update Go Dependencies
Run these commands in the cli/ directory:
cd cli && go get -u ./...
cd cli && go mod tidy
Note: go get -u updates to the latest minor/patch versions respecting the module's compatibility guarantees.
3. Update npm Dependencies
Run this command in the frontend/ directory:
cd frontend && pnpm update
This updates packages within their semver ranges defined in package.json.
4. Run Tests
Execute the full test suite:
mise run test
If tests fail: Stop here and report the failures. Do NOT attempt to rollback the changes - leave them in place so the user can review and fix manually.
5. Generate Report
After completing the updates, provide a summary report with this structure:
Dependency Update Report
Go Dependencies (cli/)
| Package | Previous | Updated |
|---|---|---|
| package-name | v1.2.3 | v1.2.5 |
npm Dependencies (frontend/)
| Package | Previous | Updated |
|---|---|---|
| package-name | ^1.2.3 | ^1.2.5 |
Test Results
- Status: PASSED/FAILED
- If failed: List the failing tests and error messages
Notable Updates
Highlight any significant updates, especially:
- Security-related packages
- Major framework updates (gin, svelte, sveltekit, etc.)
- Build tooling (vite, typescript, etc.)