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".
scripts/gates/a02-already-shipped.sh
View on GitHub#!/usr/bin/env bash
# Catalog: A2 — Claim work that's already merged in another PR
# Mitigates: PostHog #55412 trap (2026-05-02) — issue was open but PR #57145
# had already merged the principled fix. Without this check we'd have
# submitted a duplicate and burned an AI policy strike.
source "$(dirname "$0")/lib/preamble.sh"
gate_read_input
ISSUE_NUM=$(fm_field "$GATE_CANDIDATE_PATH" "issue_number")
if [[ -z "$ISSUE_NUM" || -z "$GATE_REPO" ]]; then
gate_skip "no issue_number or repo in candidate"
fi
# Check each of GitHub's three auto-close keywords. NB: gh search uses --merged
# (NOT --state=merged), and "X OR Y OR Z" is treated as a literal phrase, so
# we must run separate calls. (Lessons logged in scout's MEMORY.md.)
SHIPPED_PR=""
for KW in closes fixes resolves ; do
HIT=$(gh_safe search prs --repo="$GATE_REPO" "$KW #$ISSUE_NUM" --merged --limit 1 --json url --jq '.[0].url // empty' || /usr/bin/echo "")
if [[ -n "$HIT" ]]; then
SHIPPED_PR="$HIT"
break
fi
done
if [[ -n "$SHIPPED_PR" ]]; then
gate_block "issue already shipped in $SHIPPED_PR" "the issue is open but its fix has already merged. Post a 'safe to close?' comment on the issue (good citizen move) and pick a different candidate."
fi
gate_pass "no merged PR claims to close this issue"
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 |