d0zingcat/claude-code
1
0
Fork 0
mirror of https://github.com/instructkr/claude-code.git synced 2026-05-16 19:06:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

omx(team): auto-checkpoint worker-3 [6]

Browse Source
This commit is contained in:
bellman
2026-05-15 11:40:53 +09:00
parent 7b63c0a2eb
commit 02889d701a
4 changed files with 135 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/pr-issue-resolution-gate.md
View File

@@ -18,14 +18,28 @@ Before the Claw Code 2.0 Ultragoal can be marked complete:
## Current live snapshot
A live snapshot was captured locally during G002 execution:
A fresh non-destructive snapshot was captured locally during G011 W3 execution:
- PR snapshot: `.omx/research/github-live/open-prs.json`
- Issue snapshot: `.omx/research/github-live/open-issues.json`
- Captured on: 2026-05-14 during the active Ultragoal run.
- Observed counts: 50 open PR records and 1000 open issue records from GitHub CLI list calls.
- Command: `gh pr list --state open --limit 1000 --json number,title,state,updatedAt,url`
- Command: `gh issue list --state open --limit 1000 --json number,title,state,updatedAt,url,labels`
- Captured on: 2026-05-15T02:39:41Z during the active Ultragoal run.
- Observed counts: 51 open PR records and 1000 open issue records from GitHub CLI list calls.
- Most recent open PR in the snapshot: #3040, `fix: recognize OPENAI_API_KEY as valid auth for OpenAI-compatible endpoints`, updated 2026-05-14T11:35:23Z.
- Most recent open issue in the snapshot: #3039, `How to install skills?`, updated 2026-05-14T08:14:36Z.
- The issue snapshot hit the configured `--limit 1000`, so the final gate must treat the issue count as at least 1000 unless a higher-limit export or paginated ledger is captured.
These local `.omx/research/github-live/*` files are evidence inputs, not final proof. The final gate must refresh them and compare deltas.
These command outputs are evidence inputs, not final proof. The final gate must refresh them and compare deltas before any completion claim.
## Anti-slop triage templates
Use `docs/anti-slop-triage.md` plus the repository templates before acting on the live snapshot:
- `.github/ISSUE_TEMPLATE/anti_slop_triage.yml` records the initial issue classification, evidence, and non-destructive next action.
- `.github/PULL_REQUEST_TEMPLATE.md` adds PR classification, verification, and resolution-gate checklist items.
The anti-slop classifications are: `actionable-bug`, `actionable-docs`, `actionable-feature`, `duplicate`, `spam-or-promotion`, `generated-slop-or-hallucinated`, `unsafe-or-security-sensitive`, `not-reproducible-yet`, and `externally-blocked`.
Automation lanes may recommend labels, comments, defer/close rationales, or merge candidates, but must not merge or close remote PRs/issues without maintainer-owned approval.
## Required final evidence