taloncjones
@taloncjones
Public Skills
review-change
by taloncjones
Obtain one bounded independent development review of an implementation change.
review-change
by taloncjones
Obtain one bounded independent development review of an implementation change.
pr-status
by taloncjones
'Use for a PR status table - every open PR in this repo with its head, CI, co-review verdict at head, bench evidence, body currency, draft state and what it waits on. Trigger on "pr status", "PR table", "status of the PRs", "what are the PRs waiting on", or /pr-status [pr ...] [--repo owner/name].'
dotfiles-run-and-operate
by taloncjones
Day-to-day operation of an already-installed dotfiles machine. Load when asked to "update the dotfiles", "reload zsh", clean up leftovers from a retired plugin (its uninstall function is the only surviving entry point for both Superpowers and ECC; their install/update entry points are retired and no longer exist), run dotfiles-repair, prep a repo with setup-claude, explain claude account routing (claude-account, the claude() wrapper, work vs personal), find where machine state lives (~/.claude, ~/.claude-work, cache stamps, plugin dirs), or understand .todos/.planning worktree hydration. NOT for first-time environment setup (dotfiles-build-and-env), debugging a broken symptom (dotfiles-debugging-playbook), or Claude Code platform internals (claude-code-platform-reference).
codex-plan-review
by taloncjones
Obtain a bounded independent Codex review of one explicit frozen implementation plan.
handoff
by taloncjones
Use when the user wants to pause work, restart the runtime, change sessions, or preserve a task for another Claude or Codex session.
kickoff
by taloncjones
Use when the user wants to continue a saved task after a restart, resume from a handoff, or move an existing task between Claude and Codex.
dotfiles-diagnostics-and-tooling
by taloncjones
Use when you need to MEASURE the state of a dotfiles machine or cloud container instead of eyeballing it -- interpreting identity-doctor output, running/reading bin/dotfiles-tests, inspecting plugin state (installed_plugins.json, known_marketplaces.json), diffing live settings.json against the template, or running this skill's cloud-doctor.sh / symlink-audit.sh scripts. Trigger phrases -- "is this environment healthy", "why did identity-doctor fail", "which test suite broke", "are the plugins actually installed", "did settings drift", "audit the symlinks". NOT for fixing what you find (dotfiles-run-and-operate), rebuilding from scratch (dotfiles-build-and-env), debugging a specific symptom (dotfiles-debugging-playbook), or single-fact verification recipes (dotfiles-verification-toolkit).
dotfiles-external-positioning
by taloncjones
Load BEFORE any action that touches the public surface of this repo -- committing new file types, vendoring or deriving from upstream code, adding a dependency or plugin, publishing/README changes, or deciding whether something belongs in this repo at all. Covers what may NEVER land in the tree (secrets, employer config, 1Password vault names, per-model audit files), the enforcement stack (block_secrets hooks, retired-ECC-derived pre-commit scan, public-safety.test.sh, .gitignore), MIT/NOTICE licensing duties, the upstream trust map (the retired Superpowers, the retired ECC, the compromised GSD original), and the public/private split. Trigger phrases -- "is this safe to commit", "can this go in the repo", "add this upstream tool", "update NOTICE", "license question", "is the repo safe to be public", "should this be private". NOT for the mechanics of committing (dotfiles-change-control), running the test suites (dotfiles-validation-and-qa), or why a hook blocked you (dotfiles-debugging-playbook).
dotfiles-build-and-env
by taloncjones
Recreate any dotfiles environment from nothing -- fresh macOS, fresh Linux, claude.ai/code cloud container, or the work-identity add-on -- as numbered copy-paste runbooks with expected output at each checkpoint, plus the twelve known install traps. Load when the user says "set up a new machine", "fresh install", "bootstrap", "new laptop", "cloud container setup", "install from scratch", "add work identity", or when bootstrap.sh / bootstrap-cloud.sh / identity-setup fails mid-run. NOT for day-to-day update/plugin operations on an already-installed machine (dotfiles-run-and-operate), diagnosing a broken existing install (dotfiles-debugging-playbook), or proving a link/plugin/identity claim (dotfiles-verification-toolkit).
dotfiles-cloud-first-campaign
by taloncjones
The executable campaign runbook for making cloud/ephemeral Claude Code sessions (claude.ai/code containers) a first-class primary environment for this dotfiles setup. Load when planning or executing cloud-parity work -- "make cloud sessions first-class", "roll out plugins to another repo's cloud environment", "why aren't plugins loaded on session 1", "should the Setup script or the settings declaration carry the install", "close the machine/cloud parity gap", "was ECC rules vendoring still needed before ECC's own retirement". Phased with decision gates, exact commands, expected outputs, and fenced wrong paths with incident hashes. NOT for diagnosing a single sick container (dotfiles-diagnostics-and-tooling cloud-doctor), one-time environment rebuild (dotfiles-build-and-env), the settled incident history itself (dotfiles-failure-archaeology), or Claude Code platform mechanics in general (claude-code-platform-reference).
model-tuning
by taloncjones
Cross-model behaviors and per-family tuning deltas for the current Claude families (Opus, Sonnet, Fable) plus the model-retirement playbook. Use when authoring or pruning skills, subagent prompts, Workflow scripts, or API calls that pin a model, set effort, budget tokens, or handle safety-classifier refusals or forced-tool-use errors - when prompting for code review, frontend work, or unattended agent runs - and when a model is added, retired, or an alias moves to a new model.
claude-plan-review
by taloncjones
Obtain a bounded independent Claude review of one explicit frozen implementation plan.
repo-recall
by taloncjones
Use when answering questions about prior decisions, specs, plans, findings, todos, handoffs or session memory in the current repo -- "didn't we decide X", "what did the review say about Y", "find the spec/plan/todo about Z", "search our docs/notes/memory". Ranked SQLite FTS5 search over the repo's prose artifacts; not for code symbols (use LSP / grep).
dotfiles-research-frontier
by taloncjones
The open-problems map for this repo -- where it can advance beyond what chezmoi/stow-class dotfiles tools do (they manage files; this repo manages an AGENT operating environment). Load when asked "what should we work on next", "what are the big open problems", "where is this repo ahead of / behind the state of the art", "is there a research angle here", or when scoping a new improvement slice and you need the ratified priority list with first steps and falsifiable milestones. Each problem names its existing repo asset, three concrete first steps, and the exact measuring command that decides success. NOT the executable cloud runbook (dotfiles-cloud-first-campaign), NOT the evidence-bar discipline for landing a change (dotfiles-research-methodology), NOT settled history (dotfiles-failure-archaeology).
reconcile
by taloncjones
Reconcile my git/PR reality against Jira and fix tracking drift (untracked PRs, stale statuses, sprint hygiene) with propose-confirm-apply. Use when tidying my tracked work, before a sprint boundary, or when asked "what needs cleanup/action". Per-project config in ~/.claude/reconcile/projects.json.
wrap
by taloncjones
Use when the user is ending a session and wants the exit state verified instead of being asked "anything else?". Trigger on "good to exit", "are we done", "wrap up", "closing out", "done for the day".
brief
by taloncjones
Use for a forward-looking morning brief - what to focus on today. Aggregates time-relevant todos across all registered repos and joins them with PRs awaiting your action and your active Jira tickets. Trigger on "morning brief", "what's on today", "daily brief", "what should I work on".