dependency-update
Add, bump, or remove a crate dependency in the titi workspace safely — justification, RustSec check, lockfile, one commit. Use when a change needs a new crate or a version bump.
- License 许可
- MIT
- 所属仓库
- robertt3kuk/titi
- 最近更新
- 2026-11-02
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- dependency-update
- description
- Add, bump, or remove a crate dependency in the titi workspace safely — justification, RustSec check, lockfile, one commit. Use when a change needs a new crate or a version bump.
03 SKILL.md 正文
dependency-update
Before adding
- Can std or an existing workspace crate do it? Check
Cargo.tomlfiles first (serde,tokio,thiserror,regex,reqwest,rusqlite… are already in use). - Check the crate: last release date, downloads, maintainers, license
(must be MIT/Apache-compatible),
unsafesurface. - RustSec: search https://rustsec.org/advisories/ for the crate name, or
cargo auditif it is installed (don't install tools without asking). - Minimal features:
default-features = falsewhen defaults pull in unneeded stacks (seereqwestwithrustls-tls).
Adding
- Shared by 2+ crates → consider
[workspace.dependencies]in the rootCargo.toml; the root manifest andCargo.lockare shared files — one writer at a time (skillsupervisor-review). - Keep
Cargo.lockcommitted; CI runscargo test --workspace --locked, so a stale lockfile fails CI.
Commit
One commit per dependency change: chore(cargo): add <crate> for <why> or
chore(<crate>): bump <dep> to <ver>. Body: why this crate, what was
checked (advisories, maintenance), alternative rejected. Then skill
commit and watch CI (skill ci-and-tests).
Removing
Grep for the crate across crates/, remove it, let CI prove nothing broke.
04 同仓库更多 Skills
tui-smoke
Manually verify a titi TUI change in a real terminal and record it in docs/QA_STATUS.md. Use after changing titi-tui or titi-cli screen code, keys, slash commands, rendering, or when asked to smoke-test the chat.
supervisor-review
Playbook for the lead agent in titi that dispatches workers and accepts or rejects their output — verify artifacts not reports, return wrong work to the same worker, serialize shared files. Use when orchestrating subagents or reviewing a subagent's result.
skill-authoring
How to turn a recurring multi-step procedure in titi into a new project skill under .agents/skills, and wire it for every agent. Use when a 3+ step routine repeats, or the user says "make this a skill".
security-review
titi project security checklist for changes touching keys, providers, tools, approval, sessions, memory, or prompts. Use when a change handles credentials, runs commands, reads/writes files for the model, or when asked for a security review.
commit
Commit and push a change in titi the project way — one concern per commit, Conventional Commits with a prose body, straight to origin master, never force. Use when asked to commit, push, save, or ship a change.
code-review
titi project self-review checklist for a titi change before calling it done — error handling, tests, engine boundary, secrets, commit hygiene. Use before reporting a task complete, or when asked to review a diff.