all publishers

dcouple

@dcouple source repo

54 published skills

  1. ▌
    Investigate 5 · dcouple
    Investigate a bug or broken behavior through hypothesis-driven root cause analysis and report what is wrong without jumping straight to a fix. Use when something is failing or behaving unexpectedly.
    629 repo stars
  2. ▌
    Discussion 3 · dcouple
    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.
    629 repo stars
  3. ▌
    Implementer 2 · dcouple
    Carry out a structured implementation plan carefully and systematically, following existing repo patterns, preserving intent, and running quality checks as work progresses. Use when a plan already exists and the goal is execution.
    629 repo stars
  4. ▌
    Investigate 4 · dcouple
    Investigates bugs through hypothesis-driven root cause analysis. Automatically invoked when the user reports a bug, error, broken behavior, or something not working as expected. Use when something is broken, failing, or behaving unexpectedly.
    629 repo stars
  5. ▌
    Plan Reviewer 2 · dcouple
    Review an implementation plan for repo accuracy, fact purity, intent fidelity, reconciliation quality, and completeness. Use when a plan needs a correctness and completeness pass.
    629 repo stars
  6. ▌
    Review 2 · dcouple bundle
    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.
    629 repo stars
  7. ▌
    Implement 3 · dcouple
    Executes an approved plan by breaking work into parallelizable chunks and spawning implementation sub-agents. Automatically reviews the result for completeness. Use after a plan is approved.
    629 repo stars
  8. ▌
    Prepare Pr 3 · dcouple
    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.
    629 repo stars
  9. ▌
    Create Plan 2 · dcouple bundle
    Creates an implementation plan with thorough codebase and web research. Auto-reviews the plan after creation and iterates with user feedback. Use when planning a new feature or significant change.
    629 repo stars
  10. ▌
    Investigate 3 · dcouple
    Investigates bugs through hypothesis-driven root cause analysis. Automatically invoked when the user reports a bug, error, broken behavior, or something not working as expected. Use when something is broken, failing, or behaving unexpectedly.
    629 repo stars
  11. ▌
    Simple Plan 3 · dcouple
    Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change Z"). Investigates, proposes a lightweight plan, and implements after approval. Use this instead of /create-plan when the user wants something done, not a formal plan.
    629 repo stars
  12. ▌
    Commit 2 · dcouple
    Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
    629 repo stars
  13. ▌
    Discussion 2 · dcouple
    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.
    629 repo stars
  14. ▌
    Research Web 2 · dcouple
    Conducts extensive web research on technical topics with validated references and citations. Use when you need external documentation, library comparisons, or best practices research.
    629 repo stars
  15. ▌
    Implement 2 · dcouple
    Executes an approved plan with one primary implementation stream by default, using bounded parallel sidecars only when the write scopes are truly disjoint. Supports default Claude execution or an explicit Codex executor option. Automatically reviews the result for completeness and intent fidelity. Use after a plan is approved.
    629 repo stars
  16. ▌
    Prepare Pr 2 · dcouple
    Commits changes grouped by done-plans, rebases main, runs build and quality gates, then creates or updates a PR. Replaces the commit command. Use when you're ready to open or update a pull request.
    629 repo stars
  17. ▌
    Simple Plan 2 · dcouple
    Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change Z"). Investigates, proposes a lightweight plan, and implements after approval. Use this instead of /create-plan when the user wants something done, not a formal plan.
    629 repo stars
  18. ▌
    Do 2 · dcouple bundle
    Run the full autonomous pipeline against a work item - plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a work-item reference (issue
    629 repo stars
  19. ▌
    Investigate 2 · dcouple
    Investigates bugs through a single evidence-driven investigator, scaling from a normal root-cause pass to a deep falsifiable experiment loop. Use when something is broken, failing, or behaving unexpectedly.
    629 repo stars
  20. ▌
    Release · dcouple
    Creates or updates a staging → main release PR with a summary of all merged PRs and a prioritized four-tier testing checklist. Use when preparing a release for production.
    629 repo stars
  21. ▌
    Plan · dcouple bundle
    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.
    629 repo stars
  22. ▌
    Commit · dcouple
    Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
    629 repo stars
  23. ▌
    Review · dcouple bundle
    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.
    629 repo stars
  24. ▌
    Implement · dcouple
    Executes an approved plan directly in Codex with one primary implementation stream by default, bounded sidecars only when write scopes are truly disjoint, and mandatory review gates for completeness and intent fidelity. Use after a plan is approved.
    629 repo stars
  25. ▌
    Share Fix · dcouple
    After shipping a non-trivial fix, find related GitHub issues across the ecosystem, draft helpful human-sounding comments linking the fix and root cause, and optionally file upstream issues. Drafts must pass as human writing or the user's GitHub reputation suffers. Works on the current session's fix or retroactively on past commits/PRs. Always asks for approval before posting anything public.
    629 repo stars
  26. ▌
    Prepare Pr · dcouple
    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.
    629 repo stars
  27. ▌
    Researcher · dcouple
    Research a technical topic using a mix of web sources and local codebase context, then produce actionable guidance with citations. Use when the user wants a thorough research-oriented answer.
    629 repo stars
  28. ▌
    Simple Plan · dcouple
    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 `plan` when the change is straightforward.
    629 repo stars
  29. ▌
    Create Plan · dcouple bundle
    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.
    629 repo stars
  30. ▌
    Research Web · dcouple
    Perform technical web research using authoritative sources, synthesize the results, and save a cited research note in the repo. Use when external documentation or up-to-date behavior matters.
    629 repo stars
  31. ▌
    Codebase Explorer · dcouple
    Explore the notetake codebase to locate files, trace behavior, and document existing patterns with precise file references. Use when the task is understanding what exists, not proposing changes.
    629 repo stars
  32. ▌
    Implementation Reviewer · dcouple
    Review completed code changes against a plan, run quality checks, and call out gaps, regressions, or missing integrations. Use when implementation work needs a plan-based review.
    629 repo stars
  33. ▌
    Do · dcouple bundle
    Run the full autonomous pipeline against a work item - plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a work-item reference (issue
    629 repo stars
  34. ▌
    Codex · dcouple
    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-brief whenever one of these roles runs; not normally invoked by the user directly. Use when a pipeline stage needs its Codex sub-agent dispatched, resumed for a fix round, or re-run.
    629 repo stars
  35. ▌
    Cold Read · dcouple
    Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is finished, or any user-facing artifact. Always dispatch as a fresh sub-agent with no conversation history - the zero context is the point.
    629 repo stars
  36. ▌
    Discussion · dcouple
    Interactive back-and-forth to clarify, understand, or figure something out - an idea, an approach, a tradeoff, or a suspected bug. Use when the user wants to think out loud or explore before committing to anything - e.g. "let's discuss X", "help me understand Y", "why is Z happening", "what should we do about W". Produces clarity plus a dated decision log, not deliverables; work items are created afterward with /create-brief.
    629 repo stars
  37. ▌
    Postmortem · dcouple bundle
    Postmortem
    629 repo stars
  38. ▌
    Implementer · dcouple bundle
    Implementer role in an automated development pipeline: executes an Implementation Plan (plan.md), writing the diff while keeping the plan file true. Use when dispatched to implement a plan or apply review fixes.
    629 repo stars
  39. ▌
    Investigate · dcouple
    Investigate broken behavior using the shared evidence-driven method, scaling from a normal root-cause pass to a deep falsifiable experiment loop.
    629 repo stars
  40. ▌
    Sentry Loop · dcouple
    On-demand Sentry triage loop - sweep every project's errors over a time window, classify each issue (new / recurring / regressed, user-impacting / zero-user, real / noise), root-cause only the clusters that matter, file findings into the work tracker under the loop's label, and annotate Sentry so the state sticks. Use when the user asks to run the sentry loop, triage Sentry, "what's new in Sentry", or wants a period's errors root-caused. Report-only - fixes go through /create-brief then /do.
    629 repo stars
  41. ▌
    Investigator · dcouple bundle
    Investigator role in an automated development pipeline: reproduces a reported defect and isolates its root cause with evidence. Use when dispatched to diagnose a bug before it's written up.
    629 repo stars
  42. ▌
    Create Brief · dcouple
    Captures discussed work as a work item ready for /do - a feature brief for changes and additions (single-outcome or multi-phase), a bug brief for defects (running the investigator first if the root cause isn't established). Use when a conversation has converged on buildable work that has no work item yet - whether the user asks to capture it or convergence makes capture the obvious next step. Do not invoke for a passing idea, an unconverged thread, or work that already has an item.
    629 repo stars
  43. ▌
    Code Reviewer · dcouple bundle
    Code-reviewer role in an automated development pipeline: reviews the diff for correctness and security with file:line evidence. Use when dispatched to review an implementation.
    629 repo stars
  44. ▌
    Plan Reviewer · dcouple bundle
    Plan-reviewer role in an automated development pipeline: audits an Implementation Plan for gaps, repo accuracy, and fidelity to the work item. Use when dispatched to review a plan.
    629 repo stars
  45. ▌
    Refactor Deep · dcouple
    Refactor-deep role in an automated development pipeline: read-only comprehensive analysis of a large diff - per-layer repo-derived conventions plus a correctness hunt over new code paths, writes a prioritized plan. Use when dispatched before the final review loop on a large diff.
    629 repo stars
  46. ▌
    Web Researcher · dcouple
    Research external documentation, libraries, and best practices with cited findings for the /do plan stage.
    629 repo stars
  47. ▌
    Code Researcher · dcouple bundle
    Code-researcher role in an automated development pipeline: explores the codebase and returns current-state facts with precise file:line references. Use when dispatched to answer a question about what exists in the repo.
    629 repo stars
  48. ▌
    Refactor Simple · dcouple
    Refactor-simple role in an automated development pipeline: read-only quality analysis of the branch for small/medium diffs - repo-derived conventions, code smells, writes a plan. Use when dispatched before the final review loop.
    629 repo stars
  49. ▌
    Postmortem Loop · dcouple
    On-demand postmortem adoption loop - sweeps published postmortem comments for open system-change proposals, dedupes them against the current canonical files, lands the human-approved edits in the canonical skills repo, and posts verdict replies so the state sticks. Use when the user asks to run the postmortem loop, adopt postmortem proposals, or close the loop on postmortem findings - routinely after a batch of /do runs.
    629 repo stars
  50. ▌
    Backend Verifier · dcouple
    Backend-verifier role in an automated development pipeline: proves backend verification criteria by running the mapped tests, scripts, and commands with quoted evidence. Use when dispatched to verify implemented work.
    629 repo stars
  51. ▌
    Frontend Verifier · dcouple
    Drive browser or mobile app QA for /do, proving UI acceptance criteria and executing the PR's Manual tests checklist.
    629 repo stars
  52. ▌
    Codex Security Scan · dcouple bundle
    Run or diagnose an authorized repository scan with the official Codex Security plugin, applying repository-specific scope and reporting policy when present. Use for explicit security scans, scheduled scan runs, or Codex Security preflight failures; not for ordinary code review.
    629 repo stars
  53. ▌
    Prepare Pull Request · dcouple bundle
    Take ad-hoc changes made in-session (outside /do) to a pull request - gate them through Socrates (right approach?) and the PR reviewers (correct?), then commit, push, and open the PR in the repo's standard format. /do handles its own PR prep; this skill is for everything else.
    629 repo stars
  54. ▌
    Excalidraw Diagram · dcouple bundle
    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.
    629 repo stars