dotfiles

Monitor CI checks after pushing, detect flaky vs legit failures, and auto-fix

End-of-day counterpart to wake-me-up. Reads today's morning briefing at ~/dev/ai/notes/wake-me-up/{date}.md, asks the user what they shipped or resolved, drafts a Slack wrap-up post in the user's voice, shows the draft for explicit confirmation, then posts it on the user's behalf via the Slack MCP. Appends the posted summary back to the briefing file so the file is a full day record. Use when the user says "/closing-time", "wrap the day", "end of day post", or wants help summarizing what they did.

Commit staged/unstaged changes with a well-crafted commit message.

Create or update a GitHub PR with automatic template detection and filling

Plan, implement, and iteratively review a task end-to-end using Claude + Copilot reviewers in a linear flow.

Investigate what it would take to upgrade a library from its currently pinned version to a target version (or "latest"). Produces a migration assessment — version delta, breaking changes that apply to us, impacted files, estimated blast radius, suggested rollout — and STOPS there. Does not perform the upgrade unless the user explicitly asks. Use when the user says "investigate updating <pkg> from X to Y", "investigate updating <pkg> to latest", "we are behind on <pkg>", or "let's update <pkg> to version N".

Shepherds a PR through the repetitive loop: run qa-swarm when there are substantive changes, triage qa-swarm findings, triage AI/bot review comments, keep the branch current with its base, watch CI, and apply the `stamphog` label once green. Use when the user says "/pr-shepherd", "shepherd this PR", "babysit this PR", or wants the whole review loop driven automatically. Accepts an optional PR number or URL as argument.

Orchestrates three review skills (qa-team, paul-reviewer, xp-reviewer) into a single comprehensive PR review with inline GitHub comments. Use when the user asks for "qa-swarm", "swarm review", or wants a full multi-perspective review posted to their PR. Accepts an optional PR number or base branch as argument.

Run one review-fix iteration — review code, fix findings, simplify, and commit.

Squash all developer commits on the current branch into one. CI snapshot commits (authored by bots) are preserved in place and reported.

Pick up a stale or abandoned PR that someone (often you) started and stopped, bring it back to a shippable state, and hand it off to pr-shepherd for the active review loop. Use when the user says "take over this PR", "takeover and complete this PR", "continue <PR URL>", or pastes a PR URL and asks to finish it. Accepts a PR number or URL as argument. Distinct from pr-shepherd: the PR is dormant, not in an active review cycle.

Generate a GitHub Flavored Markdown manual test plan checklist that focuses on scenarios not covered by existing unit/integration tests. Use when the user wants to create a test plan for a PR or an implementation plan.

Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays Applies principles: data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, and data density.

Walk through items from the most recent wake-me-up briefing one-by-one and collect keep/demote/hide labels from the user. After the round, generalize the labels into natural-language rules and append them to ~/dev/ai/notes/wake-me-up/relevance.yml for confirmation. Use when the user says "/tune", "tune the briefing", "improve relevance", or wants to teach the morning briefing what's signal vs. noise.

Build a categorized morning briefing pulling from GitHub (PRs awaiting your review, your open PRs, @-mentions), Zendesk (Feature Flags team tickets), Slack (team channels, DMs, mentions — when MCP is configured), and PostHog (stub). Writes a markdown report to ~/dev/ai/notes/wake-me-up/{date}.md and surfaces blockers, review requests, in-flight work, and overnight catch-up. Use when the user says "/wake-me-up", "what do I need to do today", "morning briefing", or wants to triage their inbox.

An opinionated XP (Extreme Programming) code reviewer channeling the wisdom of Kent Beck, Ward Cunningham, Ron Jeffries, and Martin Fowler as debated on the original c2 wiki. Use this skill when reviewing code, pull requests, diffs, or designs. Triggers on any request to "review", "critique", or "give feedback on" code, or when the user asks for an XP perspective, pair programming feedback, or refactoring advice. Also trigger when users ask about code smells, simplicity, YAGNI, or whether their code is "too complex". Even if the user just pastes code and says "thoughts?", use this skill.

Write incident postmortems using the DERP model (Detection, Escalation, Recovery, Prevention). Integrates with incident.io.

Write bi-weekly sprint planning updates for the Feature Flags team. Automates PR fetching, sprint detection, and retro construction from the previous plan.

Analyze accumulated permissions and suggest smart wildcard patterns

Evaluate Copilot PR review comments, fix legitimate issues, and reply to dismissed ones.

Capture complex technical discoveries into structured, reusable notes. Use when explaining system behaviors, documenting debugging insights, or preserving knowledge.

Generate a 24-hour operational health report for a PostHog service by querying Grafana dashboards and Prometheus metrics. Produces a formatted markdown report with key metrics, anomalies, and recommendations.

Resolve git conflicts with AI-powered analysis, including mergiraf structural merging, lock file handling, and stacked PR duplicate detection.

Generate standup notes from GitHub PR activity

Start a support investigation workflow with automatic note organization

Identify unlabeled GitHub issues that may belong to a specific team