dom-sensible-contribution-flow · git:20261110.4fd9131 · 2026-11-10 · sha256 fde21a168cff018c

dom-sensible-contribution-flow git:20261110.4fd9131A

Immutable. This exact content never changes and is served at /api/v1/blob/fde21a168cff018c.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wvfln5ggbgggzcf3/fde21a168cff018cf22d91dabd6056406039353840332dd65fd8e46cd90285b9.json

Then /plugin install dom-sensible-contribution-flow@markdownregistry-wvfln5ggbgggzcf3 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: dom-sensible-contribution-flow
description: |-
    Use whenever `sensible-contribution-flow` applies.

metadata:
    internal: true
---

# Contribution Flow

Load `sensible-contribution-flow` and apply these personal contribution defaults under the global **Explicit user direction** policy. The base owns the contribution lifecycle and its authorization checkpoints.

## Implementation Review

Read and apply `super-review`’s `SKILL.md` from the same installed skills root for the coordinator’s implementation review of initial contributions and implementation revisions, including documentation changes. Pass the base workflow’s review scope and established authority to it. Leave the base’s design review and standalone read-only review routes unchanged.

Unless the user selects different stages or waives review, use the initial stage to satisfy the base’s review before commit preparation. For requests limited to working tree changes, select only that stage. Otherwise, select the full sequence, with the base’s commit preparation serving as `super-review`’s committed-target preparation. Carry the base’s commit authorization, packaging, message, and shared pull request history constraints into that operation. After later changes, apply `super-review`’s continuation requirements before declaring readiness.

Under **External services** and **Agent communication**, include `super-review`’s selected recipients and processing providers through T3 Code, required follow-ups, replacements, repeated final reviews, and disclosure of task-required repository material and non-secret context in the contribution’s existing execution checkpoint. Reuse explicit authorization that already covers those effects. When no checkpoint is otherwise needed, resolve only the uncovered reviewer exchange authorization before implementation. Loading this overlay doesn’t authorize disclosure.

## Adjacent Opportunities

Apply global **Task refinement** and **Preserve Adjacent Opportunities** with upstream fit in mind:

- **Current PR:** Include accepted improvements when they fit upstream expectations for this contribution. Sharing files or having a small diff doesn’t establish that fit.
- **Separate PR idea:** Surface an independently useful opportunity whose distinct outcome, design decision, or review burden makes it a better separate contribution. Explain the separation without implementing it or opening another PR.
- **Do not pursue:** Set aside opportunities whose benefit doesn’t justify the work.

Include accepted work in the contribution’s commit planning and review coverage, preserving its packaging constraints and shared pull request history rules.