willakins
- 61 skills
- 0 followers
- 6 hours ago last updated
- ▌ Commit · willakins bundleCreate one intentional git commit from clear local changes, name it with `write-commit-name`, push only to a safe target, and delegate to `monitor` only after explicit commit-and-monitor requests. Use for single commit, commit-and-push, or local-only requests. Do not use for multi-commit, history rewrite, PR creation, force-push, or monitor-only tasks.
- ▌ Monitor · willakins bundleMonitor existing pushed branches or pull requests by coordinating mergeability, review feedback, Codex review, gated GitHub Actions trigger commits, and CI status until every target is stable or truly blocked; `not_ready` is only an interim checkpoint while monitoring continues. Use when the user says "monitor", "watch this PR", "watch the PRs", "commit and monitor", "monitor until green and clean", asks to keep polling comments/checks/conflicts, or when another skill needs coordinated PR or pushed-branch monitoring; in drive-to-merge-ready mode, trigger PR-visible remote CI with an empty `#CI` commit only after feedback is handled and Codex is clean.
- ▌ Create PDF · willakins bundleCreate or revise polished PDF deliverables with intentional layout, typography, and deterministic source files. Use when Codex needs to build a PDF from scratch or update an existing styled PDF, especially for business documents such as project outlines, proposals, reports, summaries, implementation plans, or other static documents where preserving page size, hierarchy, tables, banners, footers, and pagination matters.
- ▌ Monitor CI · willakins bundleMonitor GitHub Actions for an existing PR or pushed branch until CI is passing, pending/not_ready, or blocked. Use for "watch CI", "monitor GitHub Actions", "watch checks", "monitor this PR's Actions", or CI handoff from monitor. Do not use to open PRs or independently repair CI; in monitor gated-trigger mode, return actionable failure evidence so monitor can repair before another empty `#CI` trigger commit.
- ▌ Fix All Specs · willakins bundleRepair current-branch RSpec failures for prompts like fix all specs or make specs pass; do not use for CI monitoring, non-RSpec tests, PR review, branch splitting, or run-only requests.
- ▌ Monitor Codex · willakins bundleEnsure Codex review is requested for the current pull request head and monitor Codex review results or concerns. Use when the user asks to request, watch, or monitor Codex review, or when another monitoring workflow needs the Codex-review half.
- ▌ Write Pr Title · willakins bundleDraft a short, descriptive pull request title when the user asks for a PR title, pull request title, to name this PR, what to call a change, or title options for a branch intended for a PR. Do not use for commit subjects, PR descriptions, release notes, or issue titles.
- ▌ Review Branch UI · willakins bundleValidate the main changed user-facing UI flow for a PR or branch with agent-browser. Use for UI review slices in merge-readiness reviews. Do not use for logic/style review, CI repair, PR publication, or branches with no UI.
- ▌ Test Coded Tests · willakins bundleDiscover the current repository's coded test runner, run the tests, and return clean JSON summarizing totals and failed test files. Use when the user asks Codex to run tests, coded tests, specs, RSpec, npm test, or produce machine-readable test failure output for a repo.
- ▌ Monitor Prod Logs · willakins bundleInspect Croft production application logs in Better Stack. Use when Codex needs to monitor or debug production logs, search recent errors, trace request IDs, tail matching log lines, inspect Better Stack source or connection metadata, or run read-only ClickHouse SQL against the croft-prod-rails Better Stack source.
- ▌ Write Commit Name · willakins bundleDraft a short git commit subject from the staged diff when a commit slice is already staged, otherwise from the exact in-scope local diff. Append `#CI` only when the requester explicitly asks to include a CI marker.
- ▌ Fix Pr Until Green · willakins bundleRepair an existing pull request's failing GitHub Actions checks until actionable CI passes or a blocker remains. Use when the user explicitly asks to get an existing PR green, fix CI on this PR, repair failing actions until green, run GitHub Actions repair, or keep debugging checks. Do not use to create or publish a new PR, or for ordinary commits that do not request Actions.
- ▌ Read Croft Prod DB · willakins bundleSafely inspect Croft production records through the read-only DigitalOcean PostgreSQL replica. Use for live Croft data questions, Sentry validation against prod rows, row counts or samples, schema-backed relationship checks, or safe read-only SQL. Do not use for writes, migrations, local dev/test DBs, non-Croft databases, or secret retrieval.
- ▌ Read Croft Staging · willakins bundleSafely inspect Croft staging data through the DigitalOcean PostgreSQL database. Use for staging-only live data questions, deploy or migration verification, Active Storage metadata checks, row counts or samples, schema-backed relationship checks, and safe read-only SQL. Do not use for writes, data repair, production data, local dev/test DBs, non-Croft databases, or secret retrieval.
- ▌ Start Rails Server · willakins bundleStart, reuse, stop, or report the local Rails development stack for the current worktree with separate terminals for Rails server, Tailwind watch, and Sidekiq, using a worktree-specific `.localhost` URL. Use when Codex needs to boot or stop the app locally, avoid port and browser-cookie collisions across multiple worktrees, or give the user the exact local URL for the running branch.
- ▌ Draft Pr For Branch · willakins bundleCreate or update a GitHub PR from the current branch: verify scope, commit only intended work, push with git, generate title/body text, open a draft PR, refresh an existing PR, or mark a draft PR ready. Do not trigger CI by default; create an empty #CI trigger commit when CI is explicitly requested.
- ▌ Fix Merge Conflicts · willakins bundleResolve an active git merge with unmerged paths by inspecting conflicts, staging intentional resolutions, and continuing non-interactively with safe CI-marker merge-message handling. Use this skill when asked to fix or continue merge conflicts; not for rebases, cherry-picks, dirty worktrees, CI failures, or PR monitoring.
- ▌ Review Branch Logic · willakins bundleReview a pull request or branch for actionable correctness bugs only: wrong base, missing auth or scoping, broken contracts, misleading tests, read/write mismatches, races, or duplicate writes. Do not use for style, UI, CI, implementation, or publishing comments.
- ▌ Review Branch Style · willakins bundleUse when asked to review PRs or branches only for style-guide, AGENTS.md architecture, UI consistency, maintainability, shared-pattern, and S* code-quality findings.
- ▌ Setup Project Files · willakins bundleCreate or refresh source files for young software projects. Use for "setup project files", "initialize this app", "scaffold the repo", "create initial structure", or aligning a young codebase with README, docs, manifests, and AGENTS instructions.
- ▌ Slack Read Messages · willakins bundleRead, list, and filter Slack messages or threads from a channel. Use when Codex needs to answer requests like "show me the last 5 messages in engineering", "read recent Slack messages from Croft engineering", "find messages by Stuart in
- ▌ Draft Pr Until Green · willakins bundleCreate or refresh a draft PR, then repair actionable CI until green or blocked. Use only when the prompt explicitly asks to run or repair CI/GitHub Actions, such as "open a draft PR and get CI green", "commit with actions", or "publish this branch and fix failing checks". Not for draft-only, existing-PR CI-only, review, ready, merge, or rebase requests.
- ▌ Repair Pr CI Trigger · willakins bundleCreate an empty `#CI` trigger commit on a pushed branch or PR; use only when the prompt or caller explicitly asks to trigger CI/GitHub Actions for an already-published branch. Do not use for failing CI fixes, new PRs, check monitoring, merge conflicts, dirty or divergent branches, or ordinary commit naming.
- ▌ Setup Manual UI Test · willakins bundleSet up a local manual UI testing environment for this Rails app by finding suitable existing local records when possible, seeding realistic fallback records only when needed, generating an authorized login entry link, starting or reusing the local app, and returning detailed step-by-step manual test instructions. Use when a user asks to manually test a UI flow, create test data for browser QA, verify a page in the Rails app, or get a link into an authenticated Croft UI state.
- ▌ Write Pr Description · willakins bundleDraft a GitHub pull request description or PR body from an exact branch or PR diff. Use for requests like "write a PR description/body", including normal PRs and bug-fix PRs; do not use for PR titles, commit messages, reviews, release notes, CI repair, or PR publication workflows unless those workflows explicitly delegate body drafting.
- ▌ Plan Feature Branches · willakins bundlePlan feature work before implementation by reading the current repo, identifying affected code, and recommending one branch, independent branches, or a stack with validation. Use when asked to plan a feature, decide one PR vs several, or figure out branch breakdown. Do not use to create branches, implement, commit, publish PRs, or monitor CI.
- ▌ Address Codex Concerns · willakins bundleValidate and address Codex review concerns on the current branch. Use when asked to triage Codex review findings, inspect review comments, decide which concerns are valid, fix only proven issues, and report each concern. Do not use for general code review, unrelated test failures, or creating new skills.
- ▌ Github Recent User Prs · willakins bundleGather recent open, draft, merged, or closed pull requests for the authenticated GitHub user across a current repo, named org, or small repo set. Use when Codex needs read-only PR activity before Airtable reconciliation, weekly shipped-work review, shipped-work summaries, or open-branch follow-up. Do not use to create, review, merge, monitor CI, or edit PRs.
- ▌ Merge Main Into Branch · willakins bundleFetch the latest `origin/main`, merge it into the current branch, resolve merge conflicts, finish the merge commit non-interactively, and push the synced branch. Use when a branch or PR is behind `main`, GitHub reports merge conflicts, or the user explicitly asks to merge `origin/main` into the current branch.
- ▌ Croft Fix Sentry Bug Pr · willakins bundleInvestigate a Croft production bug from a Sentry issue URL or issue identifier and carry it through to a clean draft PR. Use when the user asks for an end-to-end flow such as "make a draft PR to fix this bug" and wants Codex to inspect Sentry, use the production read-only replica as needed, identify the logical root cause, make a short fix plan, implement the fix in logical commits, open or refresh a draft PR, and review the branch until clean.
- ▌ Initialize Electron App · willakins bundleCreate and configure Electron desktop app repos. Use for initializing Electron, adding Electron/Vite/TypeScript desktop shell, main/preload/renderer structure, secure IPC, or macOS/Linux desktop support. Triggers include "initialize this Electron repo", "initalize this electron repo", "scaffold an Electron app", and "add Electron". Do not use for web-only apps.
- ▌ Initialize Project Docs · willakins bundleCreate or refresh the initial project setup and onboarding files for a repository, including README.md, AGENTS.md, .gitignore, LICENSE, and a docs/ folder. Use when Codex needs to bootstrap a new project, fill missing repo basics, make a young project easier to understand, establish agent instructions, or normalize core documentation for software, data, design, operations, research, or other project categories.
- ▌ Monitor Merge Conflicts · willakins bundleDetect whether a monitored pull request or branch has merge conflicts, and resolve them by delegating to the existing merge-conflict workflow. Use when monitoring should include PR mergeability, base-branch conflicts, or GitHub reports that a PR cannot be merged cleanly.
- ▌ Read Sentry Bug Reports · willakins bundleRead Sentry issue URLs, short IDs, numeric IDs, event IDs, or recent production errors. Use to summarize impact, evidence, frequency, cause, and next steps from read-only Sentry data.
- ▌ Review Branch For Merge · willakins bundleCoordinate full merge-readiness reviews for explicit PRs or branches by pinning the base and head SHA, reading PR context, running UI/logic/style review skills, deciding approval, and optionally routing selected comments for publication. Trigger for approval, merge-readiness, and full-review requests. Exclude single-slice reviews, CI fixes, implementation, monitoring, and publication-only requests.
- ▌ Setup Feature Worktrees · willakins bundleCreate planned feature branches and git worktrees from an updated base branch, optionally reusing a clean current worktree, then set up databases/task links through setup-worktree-database. Use when the user already has a branch plan or ordered branch list and wants local git/worktree setup. Do not use for branch planning, implementation, PR publication, CI repair, merge-conflict repair, or database setup alone.
- ▌ Setup Worktree Database · willakins bundleCreate isolated local PostgreSQL databases for a new Rails git worktree. Use after creating a Rails worktree or when a worktree still points at shared development/test databases; runs the bundled setup script to write local env files, copy local seed databases, and link shared VS Code tasks.
- ▌ Simplify Branch History · willakins bundleRewrite noisy feature-branch history into a smaller safe commit series. Use when asked to squash, rebase, reword, tidy, or simplify branch commits before PR review or merge. Do not use for ordinary commits, merge conflicts, CI fixes, or protected branches.
- ▌ Split Branch Into Stack · willakins bundleSplit one large branch or PR into smaller, correct, iterative branches by inspecting the diff, understanding code dependencies, and using non-interactive git commands to create mergeable slices.
- ▌ Create PDF Scope Of Work · willakins bundleCreate phase-based scope-of-work or remaining-work PDFs that read like polished implementation outlines rather than generic exports. Use when Codex needs to present validated issues, workstreams, priorities, recommended order, or definition-of-done in a styled PDF, especially for scope-of-work documents, project plans, implementation outlines, remaining-work summaries, or phase breakdowns.
- ▌ Repo Contribution Report · willakins bundleUse this skill when asked to count or rank contributors in a GitHub repo by lines added/deleted, merged PRs, approved PRs, or recent/all-time activity using local git history plus GitHub PR metadata. Do not use for PR creation, CI repair, code review, recent PR listing, or generic git stats.
- ▌ Delegate Feature Branches · willakins bundleAssign planned feature branches with existing worktrees to Codex sub-agents for parallel implementation and draft PR publication. Use when a branch plan and worktree map already exist and the user asks for delegation, workers, sub-agents, or parallel Codex execution. Do not use for planning, worktree setup, single-branch work, or monitoring-only requests.
- ▌ Digitalocean App Insights · willakins bundleInvestigate DigitalOcean App Platform health, deployments, instance sizing, CPU/memory/restart metrics, and memory pressure using the DigitalOcean API. Use when Codex needs to inspect a DigitalOcean app, diagnose production app resource pressure, correlate Sentry or app symptoms with App Platform metrics, or ask the user for the minimum read-only DigitalOcean token needed for live observability.
- ▌ Enable Remote Publication · willakins bundleUse when Codex must set up or verify GitHub remote publication after a blocked workflow, including git push auth, exact PR-head targets, force-push repair, gh PR mutation auth, app review/comment readiness, or why can't Codex push. Do not use for normal PR creation after auth works, CI monitoring, branch review, generic git help, or local-only commits.
- ▌ Github Publish Pr Comment · willakins bundlePublish a top-level pull request conversation comment to GitHub for a specific PR, after confirming the exact repo and PR target and keeping the comment body limited to the selected review item text.
- ▌ Publish Draft And Monitor · willakins bundlePublish current branch as draft PR, clean local review findings, mark ready, then hand off to monitor for Codex approval, gated empty `#CI` trigger commits, spec runs, and CI monitoring. Use for end-to-end publish-draft-and-monitor requests. Do not use for draft-only PRs, CI-only, Codex-only, branch splitting, or auto-merge.
- ▌ Review Branch Until Clean · willakins bundleReview and repair the current branch against main until no Codex findings remain. Trigger for end-to-end branch review-and-fix loops. Exclude review-only, CI-only, publication-only, branch-splitting, and single-concern triage requests.
- ▌ Airtable Create Croft Task · willakins bundleCreate Croft Airtable tasks with defaults for Will Akins in Eng Backlog Current Sprint, low priority, and a current-sprint-by-assignee view hint. Use when Codex needs to create a new Airtable task and the caller provides the task name, with optional overrides for assignee, status, priority, pipeline, table, or other task fields.
- ▌ Analyze And Fix All Skills · willakins bundleBatch analyze and repair Codex skill evaluation health across installed skill folders. Use when the user says "analyze and fix all skills", "fix every skill", "loop over all skills", "make all skills pass Waza", "repair all Chat Customizations Evaluation diagnostics", or asks to run the analyze-customization-evaluations and fix-customization-evaluation-diagnostics workflow for every Codex skill. Do not use for product code tests or non-skill repositories.
- ▌ Turn Feature Into Pr Stack · willakins bundleCoordinate feature delivery from request to branch/worktree setup, implementation, draft PRs, and CI follow-through. Use when the user wants the whole flow, including branch planning and optional explicit delegation. Do not use for review-only, CI-only, single-step implementation, or branch splitting alone.
- ▌ Github Publish Review Items · willakins bundleRoute explicit requests to publish selected local PR review items to GitHub after rechecking the reviewed PR head SHA; avoid general review, CI, code-fix, drafting, or unselected publication requests.
- ▌ Sync Recent Prs To Airtable · willakins bundleEnd-to-end sync of recent GitHub pull requests into Croft Airtable task tracking. Use when Codex needs to gather the user's recent open and recently closed PRs, compare them against Airtable tasks, create missing task records, and update existing Airtable task status so the board matches recent coding work.
- ▌ Implement In Logical Commits · willakins bundleImplement code changes safely in intentional commits when asked to implement in logical commits, commit as you go, or split work into reviewable batches.
- ▌ Setup Parallel Rails Command · willakins bundleInstall, repair, or verify the user's global `parallel rails s` terminal command. Use when the user asks to set up a cross-machine Rails dev launcher that opens a Zellij session with a focused interactive shell, silent background Rails server, stacked Sidekiq/Tailwind/Rails console panes, an open port, and a worktree-specific `.localhost` subdomain.
- ▌ Github Submit Review Decision · willakins bundleUse when submitting a final GitHub PR review decision as APPROVE, REQUEST_CHANGES, or COMMENT with a body, pinned to the reviewed commit SHA; do not use for inline comments, top-level PR comments, or mixed review items.
- ▌ Reconcile Prs To Airtable Tasks · willakins bundleCompare recent GitHub pull requests against Croft Airtable task records and decide which PRs already map to tasks, which PRs need new Airtable tasks, and which matched tasks should be updated. Use when Codex is preparing an Airtable sync, checking backlog coverage for recent coding work, or auditing whether recent PR activity is represented in task tracking.
- ▌ Analyze Customization Evaluations · willakins bundleAnalyze Waza and VS Code Chat Customizations Evaluation health for Codex skills without editing them. Use when the user mentions the VS Code "analyze" button, "analyze skills", "analyze Waza results", skill evaluation health, trigger coverage, token budget, orphaned references, missing evals, model availability, or asks for a report before fixing. Do not use for product code tests.
- ▌ Airtable Will Current Sprint Tasks · willakins bundleQuery and summarize Croft Airtable task tables with defaults for Will Akins in Eng Backlog Current Sprint while excluding In Staging and In Prod. Use when Codex needs to look up tasks by assignee, status, search text, alternate Croft task tables, or semantic Airtable views such as "By assignee" or "Current Sprint".
- ▌ Sync Airtable Task Status From Prs · willakins bundleUpdate matched Croft Airtable tasks so their status reflects current GitHub pull request state. Use when Codex already has PR-to-task matches and needs to apply the Airtable write side of the sync, especially for moving tasks forward to In Progress, Needs Code Review, or In Prod without duplicating task creation logic.
- ▌ Github Publish Inline Review Comment · willakins bundleUse when publishing one inline pull request review comment to GitHub by checking the PR head SHA, targeting a changed file line, pinning to the reviewed commit_id, and leaving the review-level body empty unless explicitly requested. Do not use for top-level PR comments, batch review publication, or final review decisions.
- ▌ Fix Customization Evaluation Diagnostics · willakins bundleDiagnose and repair Waza or VS Code Chat Customizations Evaluation failures for Codex skills. Use when the user mentions "waza evaluation failed", "Chat Customizations Evaluations", "/fix-customization-evaluation-diagnostics", "fix diagnostics", failed trigger tests, unavailable models, token budget failures, orphaned references, or asks to make a skill pass Waza. Prefer moving detail into references.