update-project-dependencies
Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-12
- Stars
- ★ 2.9k
- Forks
- 150
01 前言 Front Matter
- name
- update-project-dependencies
- description
- Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.
03 SKILL.md 正文
Update Project Dependencies
-
Record direct dependency versions from
cli/go.modandapps/frontend/package.json. Keep the update within the requested product and module scope. -
In
cli/, run:mise x -- go get -u ./... mise x -- go mod tidy -
In
apps/frontend/, runmise x -- pnpm update. -
Review manifest and lockfile changes. Do not change major versions or widen declared version ranges without a request to do so. Version ranges do not prove behavioral compatibility.
-
Run
mise testfrom the repository root. If tests fail, stop and report the failures. Leave the changes for review; do not roll them back automatically. -
Report changed direct dependency versions, relevant behavior changes, and test results. State any modules or checks that were outside the scope.
04 同仓库更多 Skills
writing-tests
Instructions and hints for writing tests.
svelte-docs
Look up official Svelte, SvelteKit, and Svelte CLI documentation.
svelte-core-bestpractices
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
session-wrap-up
Review a completed, paused, or blocked coding-agent session to identify friction, mistakes, near misses, missing context, and opportunities to improve future work. Use when the user asks to wrap up, run a retrospective, explain what issues the agent faced, capture lessons learned, or recommend improvements to repository instructions, documentation, skills, tooling, tests, or workflows. Produce an evidence-based, propose-only report; do not apply follow-up changes unless the user asks.
pr-tour
A skill that provides a guided tour of a pull request, highlighting key changes, walking the developer through the code, and explaining the purpose of each modification.