with one click
dotfiles
dotfiles contains 11 collected skills from yon, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when asked to implement an epic, a backlog of issues, or "/epic-implement N" — autonomous multi-agent execution of a GitHub epic's sub-issues, safe under a permission-bypassed session. Pass the epic number as the argument; if omitted, asks which open epic to run. A single issue goes to issue-implement.
Use when asked to implement a single GitHub issue end to end — "implement #171", "fix issue N", "pick up that bug" — where the deliverable is a reviewed PR. Epics and multi-issue backlogs go to epic-implement.
Use when capturing a feature, remediation, port/resurrection of old functionality, or any multi-issue program of work as a GitHub epic with sub-issues for later execution by separate agents — including when asked to "create an epic", "file this as issues", or "plan this so a lesser model can execute it". Single-issue-scale work (one bug/feature/chore) goes to issue-plan.
Use when capturing a single unit of work as a GitHub issue for later execution by a separate session — a bug found while debugging, a feature request, a chore, or a discovery out of scope for the current task. Triggers include "file an issue", "create an issue", "write this up as a bug". Multi-issue programs of work go to epic-plan.
Use when starting work in an unfamiliar module, when a module's `.context.md` is missing or stale, or when asked to document or understand a module's role
Use when restructuring existing code without changing behavior — extracting functions, splitting modules, or addressing tech debt and code smells
Use when auditing the project for OWASP issues, secrets, vulnerable dependencies, auth gaps, or misconfigured infrastructure
Use when deploying to staging or production, shipping a release, or pushing to an environment
Use when checking code style, running linters, formatters, or static analysis, fixing lint errors, or scaffolding a linter stack for a project
Use when running, debugging, or extending the test suite — unit, integration, e2e, property, mutation, or flaky-test management
Write, critique, and sharpen OKRs (Objectives and Key Results) so each KR is a measurable outcome the team actually controls. Use this whenever the user is drafting, reviewing, rephrasing, or grading objectives and key results, planning a quarter or fiscal year, working in an OKR tracker or goals doc, or asking "is this a good KR / good metric?" — even if they don't say the word "OKR" (e.g. "help me set goals for my team this quarter," "this metric feels gameable," "turn our strategy into measurable targets"). Applies to company, team, and individual goal-setting alike.