AGENT SKILL

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

  1. Can std or an existing workspace crate do it? Check Cargo.toml files first (serde, tokio, thiserror, regex, reqwest, rusqlite … are already in use).
  2. Check the crate: last release date, downloads, maintainers, license (must be MIT/Apache-compatible), unsafe surface.
  3. RustSec: search https://rustsec.org/advisories/ for the crate name, or cargo audit if it is installed (don't install tools without asking).
  4. Minimal features: default-features = false when defaults pull in unneeded stacks (see reqwest with rustls-tls).

Adding

  • Shared by 2+ crates → consider [workspace.dependencies] in the root Cargo.toml; the root manifest and Cargo.lock are shared files — one writer at a time (skill supervisor-review).
  • Keep Cargo.lock committed; CI runs cargo 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

robertt3kuk
robertt3kuk/titi

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.

★ 1
robertt3kuk
robertt3kuk/titi

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.

★ 1
robertt3kuk
robertt3kuk/titi

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".

★ 1
robertt3kuk
robertt3kuk/titi

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.

★ 1
robertt3kuk
robertt3kuk/titi

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.

★ 1
robertt3kuk
robertt3kuk/titi

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.

★ 1