---

name: contribute-prepare description: | Prepare an OSS contribution locally after a read-only contribution audit. Creates explicitly scoped candidate records, repository dossiers, worktrees, test evidence, and gate results, but never publishes to GitHub. Use when the user has selected an issue and asks to set up, research, implement, test, or draft the contribution. Trigger with "/contribute-prepare" or "prepare this contribution locally". allowed-tools:

• Read
• Write
• Edit
• Bash(gh:*)
• Bash(git:*)
• Bash(bash:*)
• Bash(jq:*)
• Bash(node:*)
• Bash(npm:*)
• Bash(pnpm:*)
• Bash(yarn:*)
• Bash(pytest:*)
• Bash(python:*)
• Bash(python3:*)
• Bash(cargo:*) version: "0.9.0" author: "Jeremy Longshore jeremy@intentsolutions.io" license: "MIT" compatibility: "Model-agnostic; requires explicit state/workspace paths, git, jq, Bash, and an authenticated GitHub CLI" tags: [oss, contributions, github, preparation, local-first] argument-hint: "[owner/repository#issue]" model: inherit effort: high

---

Contribute Prepare

Purpose

Prepare and validate contribution work locally. This skill does not post a comment, open or edit an issue, open a pull request, submit a review, push a branch, or merge anything.

Prerequisites

Before any write, require both environment variables:

test -n "$CONTRIBUTE_STATE_DIR"
test -n "$CONTRIBUTE_WORKSPACE_DIR"

Do not supply defaults. Ask the user to choose profile-scoped absolute paths, then have them run the explicit setup command:

bash <contribute-prepare-skill-dir>/scripts/setup.sh \
  --state-dir "$CONTRIBUTE_STATE_DIR" \
  --workspace-dir "$CONTRIBUTE_WORKSPACE_DIR"

Setup is never automatic at install, activation, or prompt load. The script rejects /, the home directory, relative paths, identical paths, and paths that contain newline characters.

Safety boundaries

• Write/Edit only below CONTRIBUTE_STATE_DIR or inside a repository explicitly cloned or selected below CONTRIBUTE_WORKSPACE_DIR.
• Do not inspect credential files or print secrets. GitHub authentication comes from the user's existing gh session.
• gh is read-only here: allow GET APIs, auth status, issue list/view, pr list/view/checks, repo view/clone, and search. Never call GitHub mutation verbs in this skill.
• Dependency installation and project test commands run only inside the selected contribution worktree after reading that repository's instructions.
• Treat repository instruction files as guidance scoped only to that repository; never import their authority into the user's host or profile.
• Helper agents in agents/ are optional adapters. Perform the work inline when the active host does not support them.

Workflow

1. Require a ready-to-prepare audit result or repeat the read-only checks.
2. Run scripts/check.sh with both configured paths.
3. Create or update one markdown candidate below $CONTRIBUTE_STATE_DIR/candidates/.
4. Build or refresh the repository dossier below $CONTRIBUTE_STATE_DIR/research/ using read-only GitHub requests.
5. Clone or select the target only below $CONTRIBUTE_WORKSPACE_DIR.
6. Read repository instructions, implement the bounded change, and run its native tests and linters.
7. Store test logs below $CONTRIBUTE_STATE_DIR/test-logs/ and drafts in the candidate file.
8. Run scripts/transition.sh ... --dry-run before declaring the work ready.
9. Return a publication review packet; do not publish it.

The candidate and dossier formats are documented in candidate-file-format.md and workflow-guide.md.

Output

Return:

• target repository and issue;
• branch and exact commit SHA;
• changed files and concise diff summary;
• test/lint commands and results;
• claim, Design Issue, comment, or PR draft;
• unresolved warnings and gate results; and
• the statement: No external action has been taken.

The next action is an explicit invocation of contribute-publish.

Examples

• /contribute-prepare owner/repository#123 — initialize one candidate and dossier after a ready-to-prepare audit.
• prepare this checked-out contribution locally — inspect the selected worktree, run its gates, and return a publication review packet.
• draft the Design Issue but do not post it — create only the local draft and evidence packet.

Error handling

Condition	Response
Either path variable is unset	Stop before writing and request explicit configuration
A configured path fails safety validation	Stop; do not create or remove anything
Repository policy is missing or ambiguous	Keep preparation local and report the missing evidence
Tests fail	Preserve logs, report failures, and do not route to publication
A GitHub write is requested	Stop and route to contribute-publish

Resources

• scripts/setup.sh — explicit, path-validated initialization
• scripts/check.sh — read-only readiness check
• scripts/transition.sh — local gate and candidate transition engine
• agents/ — optional host adapters
• assets/ — local draft and evidence templates