SkillsAdd

fudesign2008/open-skills

delivery-discipline

Optional code-delivery discipline: decide whether this run needs commit + PR/MR, then commit/push via git-commit and create or update the PR/MR. Use after verification (and OpenSpec archive when the host requires it) and before feature-branch-closeout. Do NOT use for protected-branch merge (merge-discipline) or release→main shipping (git-release-finish). Triggers — 「提交并开PR」「提交并开MR」「代码交付」「开PR」「开MR」「delivery-discipline」 / deliver code, commit and open PR, open merge requ…

First seen Aug 3, 2026

Installation

$ npx skills add fudesign2008/open-skills --skill delivery-discipline
View on skills.sh ↗ GitHub repository ↗

Summary

  • Optional code-delivery discipline: decide whether this run needs commit + PR/MR, then commit/push via git-commit and create or update the PR/MR.
  • Use after verification (and OpenSpec archive when the host requires it) and before feature-branch-closeout.
  • Do NOT use for protected-branch merge (merge-discipline) or release→main shipping (git-release-finish).
  • Triggers — 「提交并开PR」「提交并开MR」「代码交付」「开PR」「开MR」「delivery-discipline」 / deliver code, commit and open PR, open merge request.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

clanker-discipline Similar name
gbasin/clanker-discipline

Catches state bloat, grab-bag models, and mutation ambiguity from AI coding agents. Use when re…

5.7K installs
principle-type-system-discipline Similar name
cursor/plugins

Apply when designing types, reviewing a function signature, or writing code in any statically-t…

2K installs
principle-boundary-discipline Similar name
cursor/plugins

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at syst…

2K installs
memory-discipline Similar name
rohitg00/agentmemory

The session loop that makes agentmemory pay off, recall before starting work, save at decision …

1.6K installs
pre-trade-discipline-gate Similar name
tradermonty/claude-trading-skills

Evaluate a local pre-trade checklist before manual order entry, blocking planless, oversized, r…

1.2K installs
fork-discipline Similar name
jezweb/claude-skills

Audit and enforce the core/client boundary in multi-client projects. Detects where shared platf…

820 installs

Also in this package

Other skills from fudesign2008/open-skills · top by installs.

npx skills add fudesign2008/open-skills
jira-fix-workflow 73 solve-workflow 71 opsx-solve-workflow 69 opsx-jira-fix-workflow 68 typescript-check 67 android-webview-debug 67 jira-read 66 git-commit 66 opsx-jira-fix-batch 65 think-big 64

Browse all from fudesign2008/open-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,126 B
  • docs SUMMARY.md 560 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 28 installs

SKILL.md

Delivery Discipline

Shared skill — single source of truth for optional post-verify code delivery: need-delivery gate → commit/push → open or update PR/MR. Hosts declare it in dependencies and abort if missing — no silent fallback.

Layering: git-commit (commit/push) → this skill (delivery orchestration) → feature-branch-closeout (menu) → merge-discipline (merge gates). Do not fold merge or release shipping into this skill.

Prerequisite skill check

On load, verify git-commit is available; if missing, abort with install hint (npx skills add FuDesign2008/open-skills -g --skill git-commit --yes). No silent degrade.

Placeholder contracts

Placeholder Meaning Who supplies
{pr-body-extra} Host-specific PR/MR body sections (Jira link, OpenSpec path, scenario tables, etc.) Referencing host, at the call site
{commit-context} Optional commit fields (type, scope, subject, jira_id) Host or inferred from branch/diff

When this applies

After verification is green (or pendings are explicitly listed) — and after OpenSpec archive when the host requires archive before delivery — when the run may need commits and/or a PR/MR.

Not this skill: merge into a protected branch; release-tag / release→main flows; commit-only with no PR intent (call git-commit directly).

1. Need-delivery gate

Skip the rest of this skill (no commit, no PR) when any of the following holds:

Signal Meaning
Clean delivery surface No uncommitted changes and no commits ahead of the intended PR base (or no feature branch work to publish)
User declined User said this run should not deliver / no PR / analysis-only
Host marked non-delivery Host path is analysis-only or equivalent with no code (or artifact) changes to publish

When skipping: state the reason in one line and return to the host (typically feature-branch-closeout or retrospective). Do not open an empty PR.

When delivery is needed (dirty tree, ahead commits, or user/host requested PR): continue.

2. Commit / push

  1. If there are uncommitted changes: load git-commit with execute=true (unless the user asked for manual commit commands only). Pass {commit-context} when the host has Jira IDs or a fixed message format.
  2. If the tree is clean but the branch is ahead of the remote: push as part of git-commit's auto flow, or push explicitly if commit was skipped.
  3. If already committed and already pushed: continue to §3 without re-committing.

Idempotency: never create an empty commit; never re-commit the same tip “for ceremony.”

3. Open or update PR/MR

  1. Detect the remote host (gh / glab / equivalent — agent picks native CLI).
  2. If an open PR/MR already exists for this head branch: update title/body when the host supplies new {pr-body-extra}; ensure the branch is pushed.
  3. If none exists: create one against the default / protected base branch.
  4. Minimum body (always): summary of intent, changed-file overview, verification status (Executed / Pending per completion-evidence-discipline honesty when the host has verification notes).
  5. Append {pr-body-extra} exactly as the host provided (do not drop Jira/OpenSpec fields).

Stop after presenting the PR/MR URL. Do not merge.

4. Return to host

Hand back: branch name, tip SHA, PR/MR URL (or “skipped — <reason>”). Hosts then load feature-branch-closeout for merge / keep / continue (and PR-only if delivery was skipped earlier and the user later chooses open PR — closeout option 1 re-enters this skill).

Host integration

  • solve-workflow / opsx-solve-workflow: after verify (and archive for opsx), load this skill, then feature-branch-closeout, then retrospective.
  • jira-fix-workflow stage 9 / opsx-jira-fix-workflow post-archive delivery: thin-reference this skill; pass Jira/OpenSpec fields via {pr-body-extra} and {commit-context}.
  • feature-branch-closeout option “Open / update PR”: load this skill (idempotent).
  • Prefer not copying commit-message or PR-body prose into hosts beyond the field map.

Forbidden

  • Merging the PR/MR from this skill
  • Embedding merge-discipline Parts A–D
  • Requiring a PR on every host run (gate in §1 is mandatory)
  • Silent no-op when the user explicitly asked to open a PR and the tree has deliverables