jeremylongshore/tons-of-skills-marketplace / plugins/community/contributing-clanker/skills/contribute-prepare
contribute-prepare
VerifiedPrepare 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".
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_DIRor inside a repository explicitly cloned or selected belowCONTRIBUTE_WORKSPACE_DIR. - Do not inspect credential files or print secrets. GitHub authentication comes
from the user's existing
ghsession. ghis read-only here: allow GET APIs,auth status,issue list/view,pr list/view/checks,repo view/clone, andsearch. 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
- Require a
ready-to-prepareaudit result or repeat the read-only checks. - Run
scripts/check.shwith both configured paths. - Create or update one markdown candidate below
$CONTRIBUTE_STATE_DIR/candidates/. - Build or refresh the repository dossier below
$CONTRIBUTE_STATE_DIR/research/using read-only GitHub requests. - Clone or select the target only below
$CONTRIBUTE_WORKSPACE_DIR. - Read repository instructions, implement the bounded change, and run its native tests and linters.
- Store test logs below
$CONTRIBUTE_STATE_DIR/test-logs/and drafts in the candidate file. - Run
scripts/transition.sh ... --dry-runbefore declaring the work ready. - 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 aready-to-prepareaudit.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 initializationscripts/check.sh— read-only readiness checkscripts/transition.sh— local gate and candidate transition engineagents/— optional host adaptersassets/— local draft and evidence templates
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |