compuse-toolboxlisted

Use when about to hand-roll a one-off shell/Python utility for a recurring chore - finding or killing a process (pgrep -f, pkill -f); a gate's REAL exit status, not a pipe's; git across repos - branch/sync/dirty, tracked vs gitignored vs untracked, merge-conflict markers; error lines in a noisy CI log; did CI finish on my commit and pass; filtering JSONL or tallying a field over a corpus; mining a Claude Code transcript for turns or calls; is this text already present; a repo sweep that skips no gitignored file; a Windows UTF-16/BOM log grep cannot find; a rate-capped transfer or hung job; a repeated ssh key/BatchMode one-liner, scp; do old and new behave the same; the latest backup or log, not ls sort tail; could a RED baseline ever fail; disk a deleted git worktree never gave back; duplicated CLAUDE.md sections; how many source files a codebase owns; which memory level holds a fact; how often a new guard would fire on real history, and was it right; a guard's finding judged against a control.
bitranox/bitranox-skills · ★ 1 · AI & Automation · score 57

Install: claude install-skill bitranox/bitranox-skills

# compuse-toolbox A small set of tested Python jigs for recurring computer-use chores. Reach for one BEFORE hand-rolling a throwaway `pgrep`/`awk`/`jq`/`json.loads` one-liner - the jig has already handled the edge cases (self-match, exit-code traps, wrapper argv) that the one-liner gets wrong. Each jig is a self-contained PEP 723 script: run it with `uv run` (uv provisions its deps) - the one exception is `gate`, which must be launched with plain `python3`, see its row below - and get its full arguments from `--help`. Run from the skill directory, or give the full path. ## Tools | Tool | Use it when you would otherwise hand-roll...