← all publishers

dcouple

@dcouple source repo

Report this profile Claim this profile

• 40 skills
• 0 followers
• 15 hours ago last updated

1. ▌
   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.
   0
   installs
2. ▌
   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.
   0
   installs
3. ▌
   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.
   0
   installs
4. ▌
   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
   0
   installs
5. ▌
   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.
   0
   installs
6. ▌
   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.
   0
   installs
7. ▌
   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.
   0
   installs
8. ▌
   Commit · dcouple

   Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
   0
   installs
9. ▌
   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.
   0
   installs
10. ▌
    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.
    0
    installs
11. ▌
    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.
    0
    installs
12. ▌
    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.
    0
    installs
13. ▌
    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.
    0
    installs
14. ▌
    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.
    0
    installs
15. ▌
    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.
    0
    installs
16. ▌
    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.
    0
    installs
17. ▌
    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.
    0
    installs
18. ▌
    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.
    0
    installs
19. ▌
    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
    0
    installs
20. ▌
    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.
    0
    installs
21. ▌
    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.
    0
    installs
22. ▌
    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.
    0
    installs
23. ▌
    Postmortem · dcouple bundle

    Postmortem
    0
    installs
24. ▌
    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.
    0
    installs
25. ▌
    Investigate · dcouple

    Investigate broken behavior using the shared evidence-driven method, scaling from a normal root-cause pass to a deep falsifiable experiment loop.
    0
    installs
26. ▌
    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.
    0
    installs
27. ▌
    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.
    0
    installs
28. ▌
    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.
    0
    installs
29. ▌
    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.
    0
    installs
30. ▌
    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.
    0
    installs
31. ▌
    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.
    0
    installs
32. ▌
    Web Researcher · dcouple

    Research external documentation, libraries, and best practices with cited findings for the /do plan stage.
    0
    installs
33. ▌
    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.
    0
    installs
34. ▌
    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.
    0
    installs
35. ▌
    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.
    0
    installs
36. ▌
    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.
    0
    installs
37. ▌
    Frontend Verifier · dcouple

    Drive browser or mobile app QA for /do, proving UI acceptance criteria and executing the PR's Manual tests checklist.
    0
    installs
38. ▌
    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.
    0
    installs
39. ▌
    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.
    0
    installs
40. ▌
    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.
    0
    installs