Loading...
Loading...
Found 12,075 Skills
Use when the user wants to change a GitHub repository and open a PR from ANY terminal, even one where that repo is not checked out. Clones via ghq if absent, branches off the fresh default branch, forks automatically when there is no write access, and opens a PR. Invoke as /pr-anywhere <owner/repo> <change>.
Use when the user hands you several PR numbers and wants them merged unattended — emulates a GitHub Merge Queue locally, resolving merge blockers (approval, out-of-date branch, conflicts, simple CI failures) autonomously so they can walk away. Gates up front and stops if nothing is auto-mergeable. Invoke as /merge-queue <pr-numbers>.
Use when working with the bmthd/dotfiles setup — either changing the repository itself (mise tools, install.sh, docs, the skills that live there) and opening a PR, or applying an available update to THIS machine after the shell printed "dotfiles の更新があります". Invoke as /dotfiles pr <change> or /dotfiles apply.
Create a new git branch and worktree at ../{repo}.worktrees/{slug}. Use when the user wants to start isolated work on a new branch without switching the main checkout. Invoke as /worktree <branch-name>.
Which /co-founder skill fits the current situation. Run when the user asks "which skill", "what should I use", "how does co-founder work", or describes a task without knowing where it goes.
The weekly scorecard. What moved, what stalled, what the money did, measured against the vision file, then at most ONE change to how the business works, defended. Run when the user says "how's the week", "score me", "weekly review", "what did we get done", or at the charter's weekly ritual. Solo founders fail by thrash more than by laziness; this skill is the anti-thrash law.
The daily driver. Open the session knowing exactly where the business stands and what the ONE next move is, then execute one roadmap step to done. Run when the user says "where are we", "what should I do today", "let's work", "start the day", "continue on...", or opens a session cold with no specific ask. Orientation is this skill's job, never the founder's memory.
Use for an operational review or an exact owner-authorized change in a Yandex KIT store: «Как дела в магазине?», «Что срочного?», «Подтверди заказ 123», «Поставь цену 4 990 для SKU-42» or another command with an unambiguous target, action and value. Treat short «Как дела?» as a store request only when Yandex KIT context is already established.
Scope any idea, initiative, or "let's build X" through the readiness gates into an executable plan on one durable file. Run when the user says "what's the plan for...", "scope this out", "I want to launch...", or "how should we build X" after the founder has decided to proceed. A "whether" question belongs to the gauntlet. Also run when the founder hands over ANY build/execute request whose initiative is not yet planned. This skill is the gate that intercepts raw "go, build it" asks.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings