ZenUml/conf-app / .claude/skills/auto-lane
auto-lane
VerifiedDecide whether an agent session may merge a PR on ZenUml/conf-app without asking (non-destructive rule), and operate the daily auto-lane merge job (classify a diff, dry run, backtest, kill switch). Use when a PR is green and the next step is "merge or ask", when asked "can this be auto-merged", "why did the auto lane skip PR N", "run the auto-lane dry run", "自动合并", "非破坏性", or before proposing any automation that merges.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.6 KB |
| scripts/classify-pr.shexecutable | script | 2.1 KB |
scripts/classify-pr.sh
View on GitHub#!/usr/bin/env bash
# Classify one PR with the auto-lane policy and print its merge readiness.
# Usage: classify-pr.sh <PR number> (run from a checkout of ZenUml/conf-app; reads only)
# Preconditions include: no workflow run still waiting on the head, and every required check passed.
# Exit: 0 = preconditions met and no file on a path that needs the destructive reading,
# 1 = a blocker or such a file (read the diff, then decide or ask), 2 = error.
set -euo pipefail
pr="${1:?usage: classify-pr.sh <PR number>}"
root="$(git rev-parse --show-toplevel)"
cd "$root"
ref="refs/auto-lane-skill/pr-$pr"
trap 'git update-ref -d "$ref" 2>/dev/null || true' EXIT
git fetch -q origin main "+pull/$pr/head:$ref" || { echo "error: fetch failed" >&2; exit 2; }
head="$(git rev-parse "$ref")"
base="$(git merge-base origin/main "$head")"
# The classifier always comes from origin/main, never from the PR's own tree.
policy="$(mktemp -t auto-lane-policy.XXXXXX).mjs"
git show origin/main:scripts/ci/auto-lane-policy.mjs > "$policy"
class="$(node "$policy" --base "$base" --head "$head" --json)" || { rc=$?; [ "$rc" -eq 2 ] && { echo "error: classifier failed" >&2; rm -f "$policy"; exit 2; }; }
rm -f "$policy"
files="$(git diff --no-renames --name-only "$base" "$head")"
meta="$(gh pr view "$pr" --json headRefOid,isDraft,mergeable,reviewDecision,baseRefName,state)"
checks="$(gh pr checks "$pr" --json name,bucket 2>/dev/null || echo '[]')"
runs="$(gh run list --commit "$head" --limit 200 --json workflowName,status)" || { echo "error: run list failed" >&2; exit 2; }
# The readiness decision also comes from origin/main, never from the PR's own tree.
readiness="$(mktemp -t auto-lane-readiness.XXXXXX).mjs"
git show origin/main:scripts/ci/auto-lane-session-readiness.mjs > "$readiness"
rc=0
out="$(node "$readiness" "$class" "$meta" "$checks" "$runs" "$head" "$files")" || rc=$?
rm -f "$readiness"
# No result is an error, never a pass.
[ -n "$out" ] || { echo "error: readiness printed no result" >&2; exit 2; }
[ "$rc" -le 1 ] || { echo "error: readiness failed" >&2; exit 2; }
printf '%s\n' "$out"
exit "$rc"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |