Menu
SkillsMP has collected 78 skills from dcouple/skills. Open a skill to review its source and details.
Showing 40 of 78 collected skills.
The Notion bridge for work items — creates a Notion work item mirroring a GitHub issue, uploads artifacts (item.md, refs/, plan.md, wrapup.md) to it, and pulls a work item's artifacts down to ./tmp/<id>/. Used by /create-feature, /create-epic, /create-issue…
Performs a comprehensive PR code review. Reads the linked GitHub issue for context, runs quality checks, and reviews code for bugs, architecture, conventions, and frontend best practices. Posts structured findings as a PR review.
Explain one topic to a smart person who knows nothing about it, as a single HTML page that leads with a picture and earns every word, rendered per the html-explainer standards. Use when the user types /eli5 <topic>, asks for a dead-simple explainer of how…
The house standard for any skill that renders an HTML page for a person to read, covering design tokens, typography, components, diagrams, and quality gates so every generated page shares one calm, graphic-first look. Use when a skill's instructions say to…
Assess where a project actually stands against what its README, plan, or pitch promises, with every claim tested against the artifact itself rather than the docs, reported in chat and as an HTML page per the html-explainer standards. Use when someone asks…
Write a plain-language teaching note after a completed task or project so the user learns from the work, and render it as a rich HTML explainer per the html-explainer standards. Use when the user asks Claude for a learning writeup, after-action explanation,…
Write a plain-language teaching note after a completed task or project so the user learns from the work, and render it as a rich HTML explainer per the html-explainer standards. Use when the user asks Claude for a learning writeup, after-action explanation,…
Commits changes grouped by done-plans, rebases main, builds API and webapp, then creates or updates a PR. Replaces the commit command. Use when you're ready to open or update a pull request.
Fan out N blind candidates at one task, pick the strongest as the base, graft the best ideas from the losers into it, verify the result. Use when one attempt at a non-trivial artifact — a design, a tricky function, a doc — would lock in the wrong shape.
Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through options, and updates ./tmp/context.md with decisions. Use when you want to think through an approach before planning.
Sustained improvement of one named metric toward a target — measure a baseline, then loop hypothesis, implement, re-measure, accept or revert. Use for perf, bundle size, lint count, or test time. A one-off fix is /investigate; this is the loop.
Proactively orchestrate persistent RunPane issue-to-ready-PR workstreams across investigation, planning, implementation, review, PR preparation, review feedback, QA, and CI without stealing focus or repeating already-granted authorization. Use when Claude…
Have an implementation-focused discussion about a feature, bug, or approach without making code changes. Use when the goal is to think through options before planning or coding.
Proactively orchestrate persistent RunPane issue-to-ready-PR workstreams across investigation, planning, implementation, review, PR preparation, review feedback, QA, and CI without stealing focus or repeating already-granted authorization. Use when Codex or…
Post-PR refactor pass. Sizes the diff against the remote default branch, fans out refactor-simple (and refactor-deep on large changes) as fresh subagents that run blind to each other, merges their plans once with max-severity rules, shows the merged report,…
Zero-context recipient review of a finished human-facing deliverable — what is clear, what isn't, what questions they'd ask — improved with creative freedom, then repeated by a fresh-context agent until a pass changes nothing. Use after completing anything a…
Run first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks Claude to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify…
Applies a refactor plan written by refactor-simple, refactor-deep, or the refactor orchestrator's merged report — auto-fixable items first, then manual items one at a time with the user, verifying with the repo's own checks after each group. Use only after…
Read-only comprehensive analysis of the branch against the remote default branch for large features — derives conventions per layer, hunts for correctness defects in the new code paths, and writes a prioritized refactor plan to ./tmp/. Usually run by the…
Read-only code quality analysis of the branch against the remote default branch for small to medium changes — classifies the diff, derives conventions from the target repo, and writes a refactor plan to ./tmp/. Usually run by the refactor orchestrator; use…
Run first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks Codex to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify…
Prepare a branch for review by committing scoped changes, rebasing on main, running builds, and creating or updating a pull request. Use when the user wants the branch ready for PR review.
Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a PRP-style research dossier, then auto-reviews the final plan. Use when planning a new feature or significant change in Codex.
Recommend what to work on next across a Pane workspace and GitHub activity. Use when the user asks what they should work on next, what to prioritize, what is blocked, what needs review, what PRs should be merged, what issues matter, or wants a triage of…
Quick gut-check before implementing when the user directly asks you to do something. Investigates, proposes a lightweight plan, and implements only after approval. Use this instead of `create-plan` when the change is straightforward.
(foundational) Answer first, cut clutter, keep the human in it. The structural layer above line-level editing, and the standing default for anything a person reads.
(foundational) The line-level rules for prose a person will read: active voice, concrete detail, direct verbs, and the AI patterns to cut. Applies to any prose before it ships.
(foundational) Add E-E-A-T signals: explainer pages, glossary, author attribution, structured data, OG images, and SEO metadata.
(execution) Create new SEO content: blog posts, landing pages, comparison pages based on the content strategy.
(foundational) Audit and rewrite website copy for voice consistency, readability, and first-timer comprehension.
(foundational) Research, draft, reader-hat, edit, slop-gate, score process for any customer-facing deliverable.
Create Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.
Inspect and address actionable GitHub pull request review feedback with complete thread-aware state. Use when a PR has review comments, requested changes, unresolved threads, or needs proof that no actionable review thread remains.
Adversarial debate between the two model stacks — a Claude advocate vs a Codex opponent — to pressure-test one high-stakes decision before it locks, or to adjudicate a head-on conflict between the two reviewers. Use at zones 0–1 when a design fork resists…
Lean dueling-wizards ideation tournament — the two model stacks independently study a project, generate and winnow ideas, blind cross-score each other's, and probe for shared blind spots; the orchestrator synthesizes a consensus matrix whose winners become…
Run the full autonomous pipeline against a work item — plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a GitHub issue
Create Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.
Dispatches one Codex (GPT-5.6) sub-agent via `codex exec` — implementer, backend-verifier, plan-reviewer, code-reviewer, code-researcher, or investigator — and returns its report. Used by /do, /discussion, and /create-issue whenever one of these roles runs;…
Captures a discussed multi-phase workstream as an Epic Spec work item ready for /do. For a single-outcome change use /create-feature instead.
Captures a discussed feature as a lean Feature Ticket work item ready for /do. For multi-phase workstreams use /create-epic instead.