claude-code-config: Skill for Claude Code

One-shot startup triage of open PRs that have gone idle. Does not enter a monitoring loop — continuous PR-fleet monitoring remains /pr-monitor-and-manage's job.

Resolve the required detector and merge-order helper before Step 1:

resolve_script() {
  local name="$1" candidate
  for candidate in \
    "$HOME/.claude/skills-worktree/.claude/scripts/$name" \
    "$HOME/.claude/scripts/$name" \
    ".claude/scripts/$name"; do
    if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
  done
  return 1
}
FORGOTTEN_PR_TRIAGE_SH=$(resolve_script forgotten-pr-triage.sh || true)
MERGE_SEQUENCE_SH=$(resolve_script merge-sequence.sh || true)
[[ -n "$FORGOTTEN_PR_TRIAGE_SH" ]] || { echo "ERROR: forgotten-pr-triage.sh not found (checked all three paths) — forgotten PR triage unavailable" >&2; exit 1; }

When invoked by /pm Step 1D inline, $GH_USER and $FORGOTTEN_PR_DAYS are already set from the calling context. When run standalone, parse $ARGUMENTS as the days threshold (e.g. /pm-forgotten-pr 7 → 7-day threshold); non-numeric or absent values fall back to 3 safely.

Step 1: Detection

# Standalone: parse optional [days] argument from $ARGUMENTS into FORGOTTEN_PR_DAYS.
# When called inline by /pm Step 1D, FORGOTTEN_PR_DAYS is already set — skip.
if [[ -z "${FORGOTTEN_PR_DAYS:-}" ]] && [[ -n "${ARGUMENTS:-}" ]]; then
  _ARG=$(printf '%s' "$ARGUMENTS" | awk '{print $1}')
  [[ "$_ARG" =~ ^[1-9][0-9]*$ ]] && FORGOTTEN_PR_DAYS="$_ARG"
fi
# Threshold defaults to 3 days; override via FORGOTTEN_PR_DAYS (or a pm-config.md
# "Forgotten PR threshold" note resolved into it). --author defaults to @me; pass
# $GH_USER when Step 0 resolved it. The script re-validates --days and falls back
# to 3 on a non-numeric/non-positive value, so a bad override degrades safely.
DAYS="${FORGOTTEN_PR_DAYS:-3}"
"$FORGOTTEN_PR_TRIAGE_SH" --json --days "$DAYS" ${GH_USER:+--author "$GH_USER"}

forgotten-pr-triage.sh (read-only — it never closes, merges, or deletes) enumerates your open PRs, keeps those whose last activity (updatedAt, the documented age basis) is strictly more than the threshold ago, and classifies each close or merge using exactly two close signals (first match wins; otherwise merge):

• linked issue closed — the PR's Closes/Fixes #N issue is already CLOSED (rationale linked issue #N closed).
• superseded / already in main — the PR contributes zero net-new commits to main (every commit already landed, including via another merged PR, by git cherry patch-id equivalence; rationale superseded / already in main).

CI/conflict state is not a close signal — a red or conflicted PR is surfaced as a merge candidate and will fail the gate visibly downstream. Each JSON record carries number, title, url, headRefName, age_days, recommendation, and rationale, so the block below renders and the action paths act without extra gh calls. Exit 0 (including the empty set) is success; only exit 2/3 (usage / environment) is a real error to surface.