AGENT SKILL

brain-audit

Run the titi audit cycle — produce an audit report with docs/AUDIT_PROMPT.md, then fold it into docs/BRAIN.md with docs/SYNTHESIS_PROMPT.md. Use when asked to audit the project, update the brain, or refresh the project health scorecard.

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

01 前言 Front Matter

name
brain-audit
description
Run the titi audit cycle — produce an audit report with docs/AUDIT_PROMPT.md, then fold it into docs/BRAIN.md with docs/SYNTHESIS_PROMPT.md. Use when asked to audit the project, update the brain, or refresh the project health scorecard.

03 SKILL.md 正文

brain-audit

BRAIN.md changes only through this cycle.

1. Audit

  • Hand docs/AUDIT_PROMPT.md (the part below the rule) to an auditor with repo access. In omp: reviewer (@review) for the general pass, plus security for section 3–4 findings; second-opinion for a cross-check.
  • Other harnesses: one fresh read-only subagent per role (general, security). Create docs/audits/ if it does not exist yet.
  • Auditors read code, not reports. Evidence is file:line.
  • Save the raw output as docs/audits/<YYYY-MM-DD>-<auditor>.md. Commit: docs(audits): add <date> audit by <auditor>.

2. Synthesis

  • Follow docs/SYNTHESIS_PROMPT.md exactly: verify each finding against current code, tag severity, strike through resolved items with a date, never invent numbers, append the audit-history row.
  • Task follow-ups go to docs/research/STATE.md as todo.
  • Commit: docs(brain): synthesize <date> audit.

3. Report

Tell the user: top findings by severity, what changed in the scorecard, what was rejected as disproved by code.

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