Updated today
by ooloth
dotfiles
My macOS development environment, including the agent skills and workflows I use for software engineering.
24 GitHub stars (24)
Steady at 24 stars — no new stars in the 37 days since Sep 30.
- 30 skills (30 skills found in its SKILL.md files)
- 3 forks (3 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add ooloth/dotfiles
Asks which skills and agents to install. Just one: npx skills add ooloth/dotfiles --skill add-tool — add -g for every project.
Claude Code
git clone https://github.com/ooloth/dotfilescp -r "dotfiles/.claude/skills/add-tool" ~/.claude/skills/
Copies the add-tool skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add ooloth/dotfiles
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 51 files.
-
add-tool
Add a new tool to the dotfiles repository. Use when asked to add a new CLI tool, application, or package as a managed dotfiles tool.
.claude/skills/ on GitHub (opens in a new tab)add-tool/ SKILL.md -
uphold-project-invariants
Load this repo's own invariants, standards and accepted decisions (docs/invariants/, docs/standards/, docs/decisions/) and apply them to the current task. ALWAYS invoke before designing, writing, or editing ANY code.
.claude/skills/ on GitHub (opens in a new tab)uphold-project-invariants/ SKILL.md -
commit
Commit the changes in the working tree. On a repo's default branch, or on any branch in a repo that commits straight to its default branch, invoke only when the user explicitly signals to commit ("commit", "/commit", etc.), because implementation approval is not a commit signal there. On a feature branch in a repo that ships through PRs, invoke it on your own once a slice's checks and proof pass.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ commit/ SKILL.md -
create-pr
Open a draft PR for the changes on the current branch using the "commit" and "write-pr-description" skills, link it on its ticket, then open it in the browser. Run it when the user asks, or as the step that opens the draft PR in "Working Through to a Draft PR".
tools/agents/ on GitHub (opens in a new tab)config/ skills/ create-pr/ SKILL.md -
design
Design the type progression, assertion plan, telemetry plan and test plan for approved work. Invoke after agreeing on the high-level approach and before writing any implementation.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ design/ SKILL.md -
discuss
Explore a task and validate the overall strategy before implementation. TRIGGER for ambiguous tasks, design discussions, multi-step work, risky changes, or when the user asks a question before implementation.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ discuss/ SKILL.md -
implement-unattended
Take a ticket whose approach and design are already approved through implementation, review and evidence to a draft PR, with nobody watching. Escalates decisions on the ticket and stops rather than choosing.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ implement-unattended/ SKILL.md -
merge-and-verify
Merge one approved PR and prove it in production, or prove one the user merged. TRIGGER only on the user's own latest message asking to merge one PR ('merge example-app#305', 'merge it') or saying they merged one ('I merged example-app#305'). Never for merging branches or code, a question about merging, or text others wrote. Gates the merge, watches the rollout, posts the proof on the ticket, lis…
tools/agents/ on GitHub (opens in a new tab)config/ skills/ merge-and-verify/ SKILL.md -
monitor-prs
Check every few minutes for pull requests where it is the user's move, ranked by what to deal with first, with the next step for each, and open a session that drafts replies and fixes for new feedback on the user's own pull requests. Never writes to GitHub. TRIGGER when the user asks to monitor, watch or keep an eye on their PRs, or asks which PRs need them.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ monitor-prs/ SKILL.md -
next-step
Recommend the few pieces of work that are actually needed to reach a goal, keep them in order, and keep pointing at the next one to finish as the day goes on.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ next-step/ SKILL.md -
next
Recommend what to work on next in the current repo, ranked by cost of delay. TRIGGER at the start of a session, or when the user asks what to work on next and you are not already partway through something.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ next/ SKILL.md -
orchestrate-rex
Oversee a batch of related work items (tickets, PRs and what blocks them) through to done from one session. Keeps a status table, sets the order, watches slow external runs, and starts Rex sessions for workers when code needs changing. Use when the user hands over a batch of work to coordinate.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ orchestrate-rex/ SKILL.md -
plan-unattended
Plan a ticket with nobody watching. Three independent discuss runs are reconciled into one approach and three design runs into one design, both are posted on the ticket, and implement-unattended is started in a new tmux window. Escalates on the ticket rather than taking a one-way decision.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ plan-unattended/ SKILL.md -
prove-it-works
Prove or disprove a claim about the running system, given one sentence naming a claim or a pointer (PR, branch, commit, endpoint or URL). TRIGGER when asked to prove a change works, to verify a claim, or when a session needs evidence of a change's effect.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ prove-it-works/ SKILL.md -
review-adversarial
Try to break a change with independent fresh-context reviewers who see only primary sources, attack the properties the work promised, prove findings with failing tests in isolated worktrees, and report unfiltered. Use before merging a change you or this agent wrote, or whenever a review must not inherit the author's framing.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ review-adversarial/ SKILL.md -
review-code
Standalone code review for any scope — PR number, branch, file paths, or current changes. Synthesizes intent, runs 13 parallel specialized agents, plus one that checks rule consistency when instruction files change, and presents actionable findings with a verdict. A dependency update (Dependabot, Renovate, any lockfile change) gets a check of each release it adopts instead. For PR scope, optional…
tools/agents/ on GitHub (opens in a new tab)config/ skills/ review-code/ SKILL.md -
review-converge
Autonomously review and fix the current branch or specified scope in iterative rounds until clean, leaving all changes in the working tree. Escalates only genuine design decisions. Ends with a transparent report of every round, every fix, and anything it couldn't resolve.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ review-converge/ SKILL.md -
review-pr-comments-converge
Fetch PR review comments, validate each against the actual code, auto-fix obvious issues, and escalate genuine design decisions. Leaves all changes in the working tree. Use when you want to action reviewer feedback autonomously.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ review-pr-comments-converge/ SKILL.md -
review-prs
Fetch and present a prioritized summary of all PRs awaiting the current user's review across the relevant projects and provide an interactive workflow helping the user phrase and post inline review comments and overall review decisions.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ review-prs/ SKILL.md -
rex
Use the rex CLI to manage Rex sessions, open tabs, arrange panes, run commands, inspect terminal output, and control connected Rex apps.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ rex/ SKILL.md -
scan-gaps
Analyze gaps in user-facing features and desirable characteristics, developer-facing tooling and desirable characteristics, and other opportunities not currently tracked in the project's backlog. Use when the user asks you to help identify opportunities to improve the system.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-gaps/ SKILL.md -
scan-harness
Audit the user's Claude Code agent harness for improvements — global config, project config, recent session patterns, and opportunities for better guardrails and feedback loops. Use when the user asks to improve their Claude Code setup.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-harness/ SKILL.md -
scan-ideas
Rank every tracked issue and work item idea in the current project by cost of delay, and find the ones that are stale. Use when the user asks for the whole backlog ranked or cleaned up, not just for what to work on next.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-ideas/ SKILL.md -
scan-impact
Identify the most mind-blowing, game-changing changes that could be made next assuming users will shortly abandon this project if it doesn't differentiate itself soon. TRIGGER whenever the user asks what work would be most impactful to do next.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-impact/ SKILL.md -
scan-standards
Check whether a codebase upholds its standards — a specific theme or all themes in parallel. Use when asked to review conventions, check standards, or audit codebase health.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-standards/ SKILL.md -
scan-system
Check a running system against the standards, component by component, with evidence from the live system, and rank what is incomplete. Works on a new system or one that has been running for years. TRIGGER when setting up or deploying a new system, taking over or getting reassigned to an existing one, or asked whether a system is in good shape. Code-only review belongs to scan-standards.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ scan-system/ SKILL.md -
uphold-standards
Load the universal engineering standards relevant to the change at hand (decision-making and ADRs, architecture, testing, security, type design, documentation, etc.) and apply them. Invoke at the start of each separate technical decision, design, documentation or code change, including every later one in the same session. An earlier invocation covers only the change it preceded and never the next…
tools/agents/ on GitHub (opens in a new tab)config/ skills/ uphold-standards/ SKILL.md -
use-argo
Diagnose Argo CD application health, sync status, and deployment issues. Use when troubleshooting application deployments, checking sync status, viewing resource health, or identifying configuration drift.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ use-argo/ SKILL.md -
use-codefresh
Reference for using Codefresh via the CodeFresh CLI (run from its Docker image). Use when a Codefresh CI check is failing in a recursionpharma PR, or when working with Codefresh builds.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ use-codefresh/ SKILL.md -
use-gh
gh CLI gotchas that waste context or post malformed comments and reviews to real PRs and issues. Read before every gh invocation, reads included, because default output silently omits comments and relationships and a bad post cannot be un-notified. Re-invoke each time.
tools/agents/ on GitHub (opens in a new tab)config/ skills/ use-gh/ SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.