day-one-review: Cold First-Time-User Launch Audit & Remediation¶
Use day-one-review when auditing a repository from the perspective of a cold Day-1 developer installing and using it publicly tomorrow, then remediating confirmed findings and running cumulative follow-up reviews without digression.
- Source specification:
.agents/skills/day-one-review/SKILL.md - Protocol reference:
day-one-protocol.md - Governing standard: PR Review Standard v1.5.0
- Canonical role map & closure gate: Roles, skill workflows, and runtime closure
Execution defaults vs. explicit /swarm opt-in¶
- Default (no
/swarm): Runs via directinvoke_subagentor single-agent execution to stay focused and avoid/swarmboard overhead. - Explicit
/swarmopt-in: Only when the user explicitly asks for/swarm, pair withswarm-governanceusing a flat/swarmcompiled viasquad_planner(agy-squad plan --topology flat --read-only), split into category-scoped read-only specialists tailored to the target repository plus one flat Integrity Auditor (audit-<id>) (structurally matching flatself-diagnosis, generalized for any target repository).
Exact 4-stage workflow¶
- Stage 1: Cadence intake &
scratch/audit anchor: Before launchingr1, ask the user strictly which review cadence they want without asking for or injecting bug hypotheses: - Single-round cold audit (
r1only): read-only report and ship verdict, then stop. - Multi-round (
r1-> remediate ->r2cumulative): iterate until the target ship verdict passes. - Full public-launch gate (
r1-> remediate ->r2-> unanchored liveraw-final): adds a fresh unanchored consumer live trial before merge or tag. Anchor all review files underscratch/day-one-review/(or a user-designated path), confirm.gitignoreand release-tarball exclusion so audit artifacts never ship accidentally (usedocs/reviews/only if explicitly requested), and pin branch,HEADSHA, dirty delta, and runtime environment. - Stage 2: Raw, unguided initial review (
r1) with live consumer install: Enforces a strict Anti-Anchoring Rule (putting[agy-transcript-access: deny]on line 1 ofr1andraw-finalsubagent prompts wheneverAgy-Context-Saveris installed). Onr1, do not read prior review ledgers (docs/reviews/*), internal planning docs (docs/plans/*),git log, PR self-claims, or maintainer hypotheses before packing the release artifact, installing it into a disposable consumer project (normal +--ignore-scriptswhere applicable), compiling public types strictly (skipLibCheck: falsefor TypeScript SDKs), and walking the target repository live from the outside in: - First 60 seconds (
README, diagrams/jargon, Quickstart, package/site metadata) - Clean install, setup, upgrade, and rollback (fresh host,
--ignore-scripts, off-PATH, cross-OS, strict public typecheck) - Everyday usage inside an unrelated user project (zero checkout assumptions, live CLI/SDK/MCP dogfooding, error clarity, friction)
- Security and trust boundaries (
4.11 SEC: execution surface, downloads/checksums, permissions, secret hygiene, linear-time regex / ReDoS, least-privilege CI workflowpermissions:/concurrency:, uninstall cleanliness) - Packaging, CI, and release pipeline (tarball allowlist, exact artifact publish, multi-OS CI)
Write
scratch/day-one-review/day-one-review-r1.mdconforming to Standardv1.5.0Sections 1-8 (ARCH..DEP,SEC), the Cold Day-1 User-Journey Trace Matrix, and the explicit 4-tier Ship Verdict: SHIP NOW:0open P0/P1/P2/P3 actionable in-repo defects (only tracked Section 8 residuals, upstream deferrals, or informational notes remain, if any).SHIP WITH MINOR POLISH:0P0/P1/SEC blockers and at most<= 2small, localized P2/P3 polish items with zero broken consumer install, compile, SDK, or core-command contracts.FIX BEFORE RELEASE:0P0/P1/SEC blockers, but>= 3open P2/P3 items or any P2 breaking consumer compilation, installation, or core documented workflows (under Stage 3, all concrete in-repo P0-P3 defects are fixed automatically to reachSHIP NOW).HOLD BEFORE PUBLIC RELEASE: Any open P0/P1 blocker, any unresolvedSECvulnerability, or any unreviewed material category.- Stage 3: Auto-fix P0-P3, ask only on Section 8 residuals & selective resume: Keep code edits separate from review passes and checkpoint clean git state. In a Day-1 launch review, P3 findings are concrete user-facing in-repo defects and are remediated automatically alongside P0-P2, no questions asked. Reserve Section 8 (
Post-Remediation Residuals & Deferred Dispositions) as the decision gate where the agent asks the user before acting or deferring: external/upstream dependencies, intentional behavior/contract trade-offs that could break existing suites or users, policy-gated files (such as benchmark definitions), and subjective suggestions. - CPU/daemon serialization rule: Default Stage 3 remediation to a single coding subagent whenever the target repository uses native indexers, local daemons, or database locks (reserving parallel coding subagents for lightweight, independent modules).
- Pre-push checks: Run tests, strict consumer typecheck, preflight, packaging, docs/lint, and CodeQL-class
SECchecks (linear-time regex / ReDoS and least-privilege CI workflowpermissions:/concurrency:). - Interruption rule: If remediation is interrupted (rate limit, timeout, disconnect, pause), inspect
manage_subagents(Action='list')and resume ONLY the interrupted subagent(s). Never send unsolicited messages to healthy running workers and never spawn duplicate replacement subagents over existing work. Only if a subagent permanently died mid-edit, run a read-only recovery audit first (git diff + worker transcript including tool calls) before finishing only the unremediated remainder. - Stage 4: Cumulative follow-up reviews (
r2,r3, ...) & unanchored liveraw-final: Follow-up reviews build directly onr1inside the same audit directory (day-one-review-r2.mdlinkingPrior review: day-one-review-r1.md), carrying forward every prior finding ID with updated canonical statuses, re-verifying fixes across primary and affected categories, and tracking Section 8 residuals. Under the full public-launch gate (or when requested), run one fresh unanchored live consumer trial (day-one-review-raw-final.mdwith[agy-transcript-access: deny]) before merging or tagging.