AGENT SKILL

ci-and-tests

How verification works in titi — tests, fmt, and clippy run on GitHub Actions, not locally. Use when you need to check whether a change passed, or read why a CI job failed.

License 许可
MIT
所属仓库
robertt3kuk/titi
最近更新
2026-11-02
Stars
★ 1
Forks
1

01 前言 Front Matter

name
ci-and-tests
description
How verification works in titi — tests, fmt, and clippy run on GitHub Actions, not locally. Use when you need to check whether a change passed, or read why a CI job failed.

03 SKILL.md 正文

ci-and-tests

Verification for titi happens on GitHub Actions, never on a contributor's machine — nothing is meant to compile locally. The workflow is .github/workflows/ci.yml with five jobs on every push and on PRs into master: fmt (cargo fmt --all --check), clippy (cargo clippy --workspace --all-targets, not denied), audit (cargo audit against Cargo.lock — informational, continue-on-error, so an advisory appears in the job's log as a crate and version with its RUSTSEC-… id and the version that fixes it, and never reddens the run), test (cargo test --workspace --locked) and tui-smoke (the real binary on a pty, scripts/tui-smoke.py).

Read the results with gh

gh run list --repo robertt3kuk/titi --commit "$(git rev-parse HEAD)"
gh run list --repo robertt3kuk/titi --branch master --limit 5
gh run watch <run-id> --repo robertt3kuk/titi --exit-status
gh run view <run-id> --repo robertt3kuk/titi
gh run view <run-id> --repo robertt3kuk/titi --log-failed

A cancelled run was superseded by a newer push (cancel-in-progress); read the latest run instead. Exceptions to "nothing local": TUI checks (skill tui-smoke) and the atlas map (skill atlas-map).

gh run watch --exit-status blocks until the run finishes and exits non-zero if it failed. --log-failed prints only the failing steps — start there when a job is red, fix the real cause, and push another focused commit. Never weaken a test to make it pass.

Commit discipline

See docs/COMMITS.md: conventional type(scope): summary, one concern per commit, prose bodies, straight-to-master push, never force-push.

Never share a target directory between checkouts

Never point another checkout's build at this checkout's target/ — build inside the other checkout with its own target dir (or none). A binary built from a foreign tree bakes that tree's CARGO_MANIFEST_DIR into itself, so a test run through this target/ fails with a filesystem error on a file you can see on disk:

Os { code: 2, kind: NotFound }

It also fails only on the full run — a -p <crate> run of the same test rebuilds with local paths and passes — so it reads like flake. If you see this, cargo clean -p <crate> to drop the foreign artifacts and rebuild.

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

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.

★ 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