GitHub collection
dvwinck/capybara-toolbox
Imported from GitHub — is this yours?
8 skills imported from this repository.
- Stars
- 33
- Forks
- 0
- License
- MIT
Skills (8)
ar-board
Starts a local approve/reject web panel (AR board) where the user judges many agent proposals one by one, then reads the decisions from disk. Use when the user wants to judge several options one at a time (ideas, templates, features, agent-architecture improvements, video themes,
question-board
Starts a local question form (question-board) where the user answers several independent agent questions on one screen, one key per question, with options and context in view, then reads the answers from disk. Use when the agent needs several independent answers before continuing
header-footer
Configures the reply header (a line such as "🕐 14:57 · main" at the top of Claude's first reply of each turn) and the footer (Claude Code's status line - session tokens, plan limits, clock, branch, model, context) from one config file - turn each one on or off, pick fields and t
doc-truth
Checks that what a repository's documents say actually exists - cited paths, links and anchors, parity between README.md and README.pt-BR.md, and versions and the plugin list against the manifests. Read-only, no network, exit code 0/1/2. Use when the user asks to check, audit or
handoff
Writes an end-of-session note so the next session can resume the work, with the git facts collected by the tool (branch, commits ahead of the base, modified files, stashes) and the citations checked before saving - whatever does not exist is marked "[not verified]" (pt-BR "[nao v
todo-sweep
Triages the TODO and FIXME comments of the code in a local panel - each comment becomes a card, oldest first (age from git blame), the user marks Resolve, Discard or Keep (pt-BR Resolver, Descartar, Manter), and the result is a read-only report; no source file is edited. Use when
publish-check
Read-only scan of a git repository (working tree and full history) for leaks before it goes public - Claude conversation links, paths from your machine (/Users/<name>), e-mail addresses and internal names. Use when the user is about to make something public - creating a public re
tidy-board
Cleans up git branches, worktrees and stashes through a local panel. Each candidate is a card showing the proof that it is already merged, only what the user approves (Delete; pt-BR Apagar) is deleted, and anything that exists in one place only gets a backup first. Use when the u