release-head-self-e2e
Skill12 starsChanged 6 days agoMITView on GitHub
Plan and run version-aware Session API self-E2E from the latest published release tag through current HEAD inside LibrAgent: pin baseline/head SHAs, map git diff to matrix cases, dedupe prior tracking tickets, optionally create/update a GitHub tracking issue when the user explicitly authorizes writes, then orchestrate parent→ child delegates for zero-human execution and independent verification using real builtin tools and the debug-only E2E control plane (LIBRAGENT_E2E_CONTROL). Triggers: "HEAD부터 릴리스까지 E2E", "last release..HEAD E2E", "self e2e matrix", "#2565 자동", "릴리스 이후 회귀 E2E", "tracking ticket then self E2E". Not Harbor-only orchestration (Harbor is optional CI path); not Cursor libr-delegate unless the user runs from Cursor. Never invent tools; use agent__* and workspace__*.
In this repository51 other files it gives its agents.
- agents.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/react-view-transitions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-initSkill
- agy-delegateSkill
- audit-docsSkill
- code-audit-expertSkill
- computer-diagnosisSkill
- create-builtin-toolSkill
- create-prSkill
- critique-builtin-toolSkill
- doc-auditorSkill
- docxSkill
- extract-log-debugSkill
- feature-refactor-proposalSkill
- gatekeeper-loopSkill
- harbor-harness-improvement-loopSkill
- harness-eval-loopSkill
- i18n-language-standardsSkill
- jobs-trace-analyzerSkill
- lean-builtin-tool-auditorSkill
- libragent-qualitySkill
- libr-delegateSkill
- libr-tool-e2e-harness-loopSkill
- modular-large-file-refactorSkill
- performance-auditSkill
- pptxSkill
- producer-loopSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- vercel-react-view-transitionsSkill
- readme-showcase-syncSkill
- refactor-builtin-toolSkill
- release-managerSkill
- review-local-changesSkill
- review-pr-commentsSkill
- science-searchSkill
- setup-wizardSkill
- skill-creatorSkill
- soul-awakeningSkill
- sqlite-analyzerSkill
- sync-pending-approvalsSkill
- tool-creatorSkill
- trace-analyzerSkill
- trace-eval-loopSkill
- vitepress-doc-syncSkill
- worker-loopSkill
- x-cliSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 22
Read references/scopes.md before acting.
- Very specific: line 78
If ambiguous, stay in read-only and ask one question.
- Very specific: line 114
Search existing GitHub issues (title/body keywords: release-head-self-e2e, baseline tag, #2565).
- Very specific: line 122
Only in github-write scope.
- Very specific: line 151
Update progress.jsonl and per-case folder under .libragent/work/release-head-self-e2e/<run-id>/cases/<id>/.
- Very specific: line 163
If github-write: comment on tracking issue with summary + artifact paths (no secret values).
- Distinctive: line 164
Do not merge or change default settings.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release → HEAD self-E2E
Internal LibrAgent workflow to turn last release..HEAD into a deduped E2E plan, an optional GitHub tracking ticket, and delegated unattended runs with independent verifiers.
Read references/scopes.md before acting. Default is read-only / dry-run until the user names a scope.
Integrate — do not fork
| Need | Use |
| Child spawn / isolation | bundled delegate |
| Proof-before-done verifier child | delegation-eval-loop |
| Matrix + Harbor tasks | benchmarks/harbor/libragent-session-e2e-matrix/ |
Debug approvals / user prompts (ui__askUser, storeAs) | LIBRAGENT_E2E_CONTROL=1 + /api/e2e-control/* (debug build only) |
| Optional external CI batch | pnpm bench:session-e2e* (Harbor); secondary to this skill |
| Cursor HTTP harness | .agents/skills/libr-delegate (out-of-app only) |
Hard rules
- Zero-human for every case the repo can run unattended; otherwise mark
blocked/platform-unsupported— neverpassand never “needs-input”. - No rerun-until-green; one honest attempt per case unless the user orders a rerun.
- Failures get a diagnosis, not silent retry loops.
- No fabricated tools — only names from the live tool list (
agent__*,workspace__*, etc.). - Parent survives child stop —
agent__stopSessionon children only; parent keeps orchestrating. Outer app restart/crash tests may use a watchdog; nothing else. - Preserve protections: release has no E2E routes; dev needs explicit opt-in; loopback + capability header; isolated data dir — never production profile or real secrets.
- Independent verifier accepts only objective artifacts (API messages JSON, workspace files,
verifier scripts, Harbor
session_e2e_evidence.json) — not child prose alone. - No product code fix / merge / global settings in this skill unless the user separately authorizes it.
- Creating this skill or loading it does not grant standing permission to open GitHub issues.
Known product limits (honest)
These remain outside full #2565 unattended coverage (see PR #2632):
- E2E control drives user prompts (
ui__askUserquestions andstoreAs/requireUserInputsecret inputs, via the shared pending-user-prompt) and tool approvals. There is no separate interactive-shell control surface. - Native GUI paths outside the app window are not drivable from the control plane.
- Full matrix still needs Windows or Linux desktop debug beside the app; cloud/Linux without the app cannot claim native GUI E2E.
Mark dependent checklist rows blocked with reason; continue independent cases.
Phases
0. Confirm authorization scope
Parse the user message for one of:
| Scope | Allowed |
read-only | Pin SHAs, diff, read manifest, read GitHub (no writes), write local plan under .libragent/work/ |
plan | Above + propose case list + ticket body draft (still no GitHub POST) |
github-write | Create/update tracking issue once when user explicitly says so (e.g. “이슈 올려”, “create tracking issue”) |
execute-e2e | Run delegated children + verifiers; requires debug app + LIBRAGENT_E2E_CONTROL=1 on isolated profile |
If ambiguous, stay in read-only and ask one question.
1. Pin baseline and HEAD
From the repo root (absolute workspacePath / workspaceOverride="current"):
python3 .agents/skills/release-head-self-e2e/scripts/pin_release_range.py \
--repo . --json > .libragent/work/release-head-self-e2e/<run-id>/pins.jsonScript behavior:
- Picks latest annotated/lightweight git tag reachable as ancestor of
HEAD(default: skips-*alpha*,-*beta*,-*rc*,-*dev*prerelease names). - Sets
baselineSha= tag peel,headSha=HEAD, verifies ancestry; if no tag or tag not ancestor → explicit error object (no silent fallback).
2. Map diff → E2E cases (version-aware)
- Load
benchmarks/harbor/libragent-session-e2e-matrix/coverage-manifest.json. - Run hints (optional):
python3 .agents/skills/release-head-self-e2e/scripts/map_diff_to_cases.py \
--repo . --baseline "$(jq -r .baselineTag pins.json)" \
--manifest benchmarks/harbor/libragent-session-e2e-matrix/coverage-manifest.json \
--json > case-hints.json- Human/agent merge: hints are suggestions only — ground each selected case in
git log/git diffpaths and the issue #2565 expectation text. Writeplan.mdwith: case id, why in range, risk, runner (harbor-task|delegate-brief|blocked).
3. Dedupe prior tickets
- Search existing GitHub issues (title/body keywords:
release-head-self-e2e, baseline tag,#2565). - Merge with completed evidence paths cited in comments; do not re-run
passcases unless user requests. - Record
dedupe.mdwith kept/skipped cases and links.
Requires github-write to post; otherwise output draft only.
4. Tracking ticket (optional)
Only in github-write scope. Single tracking issue per pinned baselineSha..headSha pair.
Body must include: pins, plan table, artifact dir, explicit “no secrets” policy, blocked list.
Link confirmed product failures only within user-granted write scope.
5. Execute self-E2E (execute-e2e)
Preconditions
- Debug LibrAgent (
pnpm tauri devor debug build), disposable data dir. LIBRAGENT_E2E_CONTROL=1. The capability token is harness-side only: the external harness reads it from the disposable instance data dir. Agents and child briefs never receive token material.LIBRAGENT_E2E_SYNTHETIC_SECRETfor masked-value fixtures only.- Serialize: one case at a time on one app instance (queue file
queue.json). - Prompt resolution scope: the only auto-resolver today is Harbor's trial
poll loop, which watches its own session. Executor children spawned via
agent__spawnSessionhave nothing answering theirrequireUserInputprompts — route those cases (e.g. B-3 interactive echo) to the Harbor runner, or mark themblockedwith reasonno in-app prompt resolver.
Parent (orchestrator)
- Load
@skill:delegatemechanics; keep workspace shared when children need repo + manifest. - For each runnable case:
- Spawn executor child (
waitForResult=falsefirst if parallel planning; serialize runs). - Brief: self-contained task, exact matrix id, synthetic secret policy, deliverable = evidence paths + API excerpt pointers.
- Poll
agent__checkSessionwith backoff; onpaused, oneagent__messageToSessionresume attempt.
- Spawn executor child (
- Spawn verifier child with no executor transcript as sole proof — pass
references/verifier-brief.md+ paths to rawmessages.json, workspace outputs, Harbor evidence. - Update
progress.jsonland per-case folder under.libragent/work/release-head-self-e2e/<run-id>/cases/<id>/. - On unsupported driver →
blockedwith reason; continue queue. - Cleanup: executor terminate/delete after evidence harvest; verifier separate session; parent remains.
Negative controls (delegate brief or Harbor test_outputs.py patterns):
- E2E routes 404 without opt-in; wrong capability header rejected; stale execution id rejected; synthetic secret absent from logs in verifier grep rules.
6. Closeout
summary.md: pass / fail / blocked counts, diagnosis per fail, limits section.- If
github-write: comment on tracking issue with summary + artifact paths (no secret values). - Do not merge or change default settings.
Artifact layout
.libragent/work/release-head-self-e2e/<run-id>/
pins.json
case-hints.json
plan.md
dedupe.md
queue.json
progress.jsonl
summary.md
cases/<case-id>/
executor-messages.json
verifier-verdict.md
evidence/...Usage examples
Full command recipes: references/usage.md.
References
- scopes.md — authorization matrix
- usage.md — release→HEAD ticket + full self-E2E examples (bash + PowerShell)
- verifier-brief.md — independent child template
- executor-brief.md — unattended runner child template
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

