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/a05-issue-still-open.sh
View on GitHub#!/usr/bin/env bash
# Catalog: A5 — Issue is still OPEN right now (not closed since dossier built)
# Mitigates: lingdojo/kana-dojo #15441 trap (2026-05-03) — issue was OPEN at
# 04:54Z when scout shortlisted it; CLOSED at 05:00Z (NOT_PLANNED) by
# maintainer killing a bot-generated cron issue. Our dossier and the existing
# A1/A2 gates wouldn't have caught it because they check assignees and
# already-shipped, not state. This is the simplest gate to write and the
# highest-value catch — bot-generated issues at active repos can close
# minutes after discovery.
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
STATE_JSON=$(gh_safe issue view "$ISSUE_NUM" --repo "$GATE_REPO" --json state,stateReason,closedAt --jq '{state, stateReason: (.stateReason // ""), closedAt: (.closedAt // "")}' || /usr/bin/echo "")
if [[ -z "$STATE_JSON" ]] ; then
gate_skip "couldn't fetch issue state"
fi
STATE=$(/usr/bin/printf '%s' "$STATE_JSON" | jq -r '.state')
REASON=$(/usr/bin/printf '%s' "$STATE_JSON" | jq -r '.stateReason')
CLOSED_AT=$(/usr/bin/printf '%s' "$STATE_JSON" | jq -r '.closedAt' | /usr/bin/cut -c1-19)
if [[ "$STATE" == "CLOSED" ]] ; then
gate_block "issue is CLOSED (reason: ${REASON:-unspecified}, closed at ${CLOSED_AT:-unknown})" "issue closed since shortlist. If reason is COMPLETED, fix already shipped — pick a different target. If NOT_PLANNED, maintainer rejected the work — drop the candidate."
fi
gate_pass "issue state = OPEN"
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 |