@chrono-meta/fh-gate 1.0.3 → 1.2.0

package/plugins/fh-meta/skills/harvest-loop/SKILL.md

@@ -0,0 +1,231 @@
+---
+name: harvest-loop
+description: A self-evolution pipeline that runs automatically after field sessions end. field-harvest (pattern extraction) → contention-layer (collision signals) → [Agent(subagent_type="challenger") + persona-innovator parallel] → synthesizer (challenger/innovator collision harvest) → Critic isolated Agent (SAGE automated critique) → harness-doctor (health check) → verify-bidirectional (consistency validation) → curator (skill lifecycle management) — 8 steps. Session learnings are automatically absorbed back into the FH ecosystem so the harness evolves on its own. In the main development environment, runs automatically at session end. For external FH users, proposes execution first. Triggered by "session harvest", "learning absorption", "fh evolution", or "harvest-loop". (The phrase "run the pipeline" is ceded to pipeline-conductor to avoid a trigger collision — for end-to-end verification sweeps use pipeline-conductor.)
+user-invocable: true
+allowed-tools: ["Read", "Write", "Bash", "Grep", "Glob", "Agent"]
+model: opus
+---
+
+# harvest-loop — Field Session → FH Self-Evolution Pipeline
+
+> Automatically absorbs patterns/conflicts/discoveries from field sessions back into the FH ecosystem.
+> Internalizes as a pipeline the return loop from field projects to the harness that was previously done manually.
+> One of the core functions is real-time detection and blocking of **Semantic Drift** — where agent terminology gradually diverges in meaning as sessions grow longer.
+
+## Operation Modes
+
+| Mode | Description | Trigger |
+|---|---|---|
+| **Forced mode** | Auto-runs at end of local development session. Executes without approval, only confirms final suggestions | Session wrap-up rules in hub CLAUDE.md |
+| **Lightweight mode** | Immediate harvest after Wave completion. Skip Steps 3/3.5/4 — prioritize fast recording | agent-composer Step 4-c (2+ new files or 3+ existing files changed, **or M-tier resolved**) |
+| **Proposal mode** | External FH users — confirms "run harvest-loop?" before executing | User utterance or `/harvest-loop` |
+
+**Simplification guard**: Sessions that only browsed/explored (no code changes or outputs) auto-skip even in forced mode.
+
+**Lightweight mode Done When**:
+```
+Step 0 (Regression Guard) + Step 1 (field-harvest) + Step 2 (contention-layer) + Step 5 (verify-bidirectional) complete
++ harvested pattern summary 1~3 lines output
++ "run full harvest-loop?" proposed (if patterns found)
++ [Card update prohibited] Do NOT update reference_next_session_starter.md in lightweight mode alone
+```
+
+**Early Trigger** (mid-session): Same pattern 3+ times · same skill fails 2+ consecutive times · session 2+ hours elapsed → "Early harvest condition detected. Run mid-session harvest?" If Y → field-harvest → contention-layer → verify-bidirectional only.
+
+---
+
+## Pipeline Structure
+
+```
+Session end
+    │
+[Step 0-a] FH asset change detection → auto-quench
+    │  git diff --name-only HEAD | grep -E "SKILL\.md|\.claude/rules/|templates/|CLAUDE\.md"
+    │  → 1+ FH assets changed: run full 3-axis gate
+    │  → No changes: proceed to Step 0-b immediately
+    │
+[Step 0-b] Card cross-check — reconstruct completed items (no memory dependency)
+    │  Read reference_next_session_starter.md + fh_completed_{today}.md + git log
+    │  → Generate removal candidate list from 3-source cross-check
+    │
+[Step 0-c] Edit Manifest Verification + Memory Hygiene
+    │  edit-manifest VERIFY: check pending predictions in edit_manifest.yaml
+    │  memory-hygiene scan: staleness check on memory/*.md entries (skip if < 7 days)
+    │
+[Step 0] Regression Guard
+    │  Check: does anything from this session conflict with or regress a validated skill?
+    │  → Regression detected: flag, route to contention-layer
+    │  → No regression: proceed
+    │
+[Step 1] field-harvest
+    │  Scan field git diff / outputs → extract patterns (proceed if 3+, skip if fewer)
+    │
+[Step 2] contention-layer
+    │  Compare patterns ↔ existing FH skills → collision = new skill candidate signal
+    │
+[Step 3a] challenger (Agent)     [Step 3b] persona-innovator  ← parallel
+    │  Attack existing skills         Propose new skill candidates
+    │
+[Step 3.5] synthesizer
+    │  Cross-synthesize attack ↔ proposal → readjust grades (HIGH/MED/LOW)
+    │
+[Step 3.75] Critic (isolated Agent — SAGE pattern)
+    │  Independent critique of synthesizer proposals → PASS / CONDITIONAL PASS / FAIL
+    │
+[Step 4] harness-doctor
+    │  Health check when adding candidates (Done When exists? ≥70% overlap?)
+    │
+[Step 5] verify-bidirectional
+    │  Bidirectional consistency check on candidate skill
+    │
+Output final proposal list → Y: PR creation / N: persist to tracks/_meta/fh_signal
+    │
+[Step 6] Curator lifecycle review (auto-run after Y)
+    │  SKILL.md STALE/merge candidates + Memory self-correction
+```
+
+---
+
+## Execution Instructions
+
+### Step 1 — field-harvest
+`/field-harvest --since 1d` — Fewer than 3 patterns → auto-skip + output "no session harvest targets".
+
+### Step 2 — contention-layer
+`/contention-layer [field-harvest output patterns]`
+
+| Collision type | Routing |
+|---|---|
+| Overlaps with existing skill | Existing skill enhancement candidate |
+| New area not covered | New skill candidate |
+| Two skills conflict | Mediation skill candidate |
+
+### Step 3 — Parallel challenger + innovator
+**3a challenger**: "Does this discovery overturn existing skill X?" / "Doesn't existing skill already handle this?" / "Does adding this simplify or complicate FH?"
+**3b innovator**: Field pattern → abstraction → naming candidates + Done When draft required.
+
+### Step 3.5 — synthesizer
+
+| devil attack | innovator proposal | synthesizer verdict |
+|:---:|:---:|---|
+| S-tier attack | Proposal for that area | **HIGH** — immediate reflection candidate |
+| S-tier attack | No proposal | **HIGH** — fix existing skill weakness immediately |
+| No attack | Proposal exists | **MED** — re-review in next wave |
+| Attack overturns proposal | — | Proposal **rejected** — persist as fh_signal on hold |
+
+**Fallback** (deep-insight not installed): Inline synthesis. Apply same judgment matrix. If quality low → Step 3.75 Critic processes as CONDITIONAL PASS.
+
+**Step 3.5-X** (optional): Cross-session 2nd validation when 2+ HIGH-grade items exist. External CLI (gemini/codex) or cross-session Claude. Items flagged as over-promoted → downgrade HIGH → MED.
+
+> **Detail**: See `SKILL_detail.md §Step3-5X` — bash execution scripts for external CLI and cross-session Claude fallback — read when running Step 3.5-X validation.
+
+### Step 3.75 — Critic (Isolated Agent)
+
+> Source: SAGE (arXiv 2603.15255). Isolation = Critic does not inherit synthesizer reasoning chain → resolves Cost of Consensus.
+
+Critic evaluation: Done When logic validation · failure mode exploration (2+ edge cases) · claim vs. implementation alignment · scope appropriateness (Too Narrow / Too Broad).
+
+FAIL routing: First FAIL → 1 re-synthesis allowed. FAIL after re-synthesis → auto-persist as `fh_signal` on hold. Maximum retries: **1**.
+
+> **Detail**: See `SKILL_detail.md §Step3-75` — Critic isolated Agent() call format, evaluation items table, FAIL routing, Post-Core-Skill Critic connection — read when executing Step 3.75.
+
+### Step 4 — harness-doctor
+`/harness-doctor --scope new-candidates` — Check: Done When exists · ≥70% overlap with existing skills · self-reference structure.
+
+### Step 5 — verify-bidirectional
+`/verify-bidirectional [new skill draft]` — If A references B, does B back-reference A?
+
+### Step 6 — Curator Lifecycle Review
+
+**6-1 SKILL.md Lifecycle**: 30+ day unused → [STALE] candidate. `pinned: true` → never touch. ≥70% overlap → merge candidate suggestion. **> 300 lines AND no `SKILL_detail.md`** → propose `/skill-splitter` (governance-semantic split — not compression; the grew-through-harvest pattern is a natural split trigger).
+
+**6-1-a Archive-candidate auto-tag**: When 0 invocations in 30 days detected (cross-check `tracks/_meta/skill_usage.md`), auto-append `#archive-candidate` tag to that skill's CATALOG.md entry. No file deletion — tag only. User reviews tagged entries at next session start.
+
+**6-2 Memory Self-Correction**: INDEX-ORPHAN (in MEMORY.md but file missing → auto-remove) · FILE-ORPHAN (file exists, not indexed → confirm with user) · MEM-STALE (30+ day unmodified → confirm with user).
+
+**Memory curator safety**: Only INDEX-ORPHAN removal is auto-allowed. Actual file deletion absolutely prohibited without explicit approval. `type: reference` items with 🔑 keywords excluded from STALE detection.
+
+**6-a Skill Usage Leaderboard**: Record skills called this session in `tracks/_meta/skill_usage.md`. Flag 4+ weeks no-call → deprecation candidate.
+
+**6-b Harness Evolution Cadence** (4-week cycle): Scan skills with `complexity_routing`. Aggregate escalation records from `fh_signal_*.md`. Valid conditions = keep; never activated in 4 weeks = removal candidate; pattern in fh_signal = addition candidate. No auto-modification — output candidates then require user approval.
+
+> **Detail**: See `SKILL_detail.md §Step6-Detail` — bash scripts for STALE detection, memory scan, skill usage leaderboard, evolution cadence aggregation — read when executing Step 6.
+
+---
+
+## Observability Hook (glass-box self-improvement)
+
+Every evolution decision must leave a 3-part trace in `tracks/_meta/edit_manifest.yaml`:
+- **(a) what changed** — file + diff summary
+- **(b) predicted effect** — `predicted_impact` + `predicted_measurable_by`
+- **(c) verify checkpoint** — `validation_status` flipped at next Step 0-c VERIFY
+
+A proposal accepted without a recorded prediction is a black-box edit — flag, do not silently apply.
+
+> **Detail**: See `SKILL_detail.md §Observability` — full observability hook spec and trace format.
+
+---
+
+## Output Format
+
+```
+## harvest-loop Execution Results
+
+Session: [date] [project name]
+field-harvest: [N patterns extracted]
+contention-layer: [N collision signals]
+synthesizer: [HIGH N / MED N / rejected N]
+
+### Final Proposals (sorted by synthesizer grade)
+| # | Type | Target | Grade | devil | innovator | synthesizer verdict |
+|:---:|---|---|:---:|---|---|---|
+
+→ Y: Create PR / draft skill file
+→ N: Persist to tracks/_meta/fh_signal_YYYY_MM_DD_{slug}.md
+
+### [Required final step] Session card update (proof gate)
+Read reference_next_session_starter.md → apply Step 0-b removal list → add new priorities
+→ output "BEFORE N items → AFTER M items (removed: [list])" — required
+→ No diff (N=M) = warning + Step 0-b re-check obligation
+
+**Natural-language close (4th source)**: Even without git log match, items with these patterns stated in session → treated as closed, remove immediately:
+- "not possible / confirmed impossible" · "no response + N weeks elapsed" → abandoned
+- "mutual citation confirmed" · "merged" · "cancelled" · "no longer needed"
+- User says "stop monitoring" · "close this" · "remove it"
+```
+
+> **Detail**: See `SKILL_detail.md §Output-Detail` — 2-source mode (when fh_completed absent), exact match criteria, natural-language close edge cases — read when reconstructing session card without fh_completed file.
+
+---
+
+## Linked Skills
+
+| Situation | Linked skill |
+|---|---|
+| 3+ new skill candidates | `/agent-composer` for dispatch plan |
+| Design existing skill enhancement direction | `/meta-prompt-builder` |
+| Validate candidates from external user perspective | `fh-meta:hub-persona-auditor` |
+| Review before sharing with team | `/apex-review` |
+| Self-marketing pattern discovered as HIGH P10 | `/harness-doctor --lint` auto-propose |
+| Edit predictions to verify / rejected buffer | `fh-meta:edit-manifest` (Step 0-c) |
+| Stale memory entries to re-verify | `fh-meta:memory-hygiene` (Step 0-c) |
+
+---
+
+## Done When
+
+```
+All stages Step 0-c → 0 → 1 → 2 → 3 (parallel) → 3.5 → 3.75 → 4 → 5 complete
++ Step 0-c: edit-manifest pending entries verified + memory-hygiene scan run
++ Step 3.75 Critic verdict received (PASS/CONDITIONAL PASS/FAIL stated) before Step 4
++ synthesizer grade readjustment complete (rejected candidates separated)
++ Final proposal list output (sorted by HIGH/MED)
++ User Y/N approval gate complete
++ (If Y) Step 6 Curator complete
+  → 6-1: STALE candidate list + merge candidates
+  → 6-2: INDEX-ORPHAN/FILE-ORPHAN/MEM-STALE detection results
++ [Required] reference_next_session_starter.md delta update complete
+  → BEFORE N items → AFTER M items diff output required (proof gate)
+  → No diff (N=M) = warning + Step 0-b re-check
+  → Completed items remaining = bug (Done When not met)
+```

package/plugins/fh-meta/skills/harvest-loop/SKILL_detail.md

@@ -0,0 +1,201 @@
+---
+name: harvest-loop-detail
+description: Detail file for harvest-loop — bash scripts for Step 6 curator, observability hook spec, Step 3.5-X bash, Critic Agent call format. Load when executing a specific step.
+load: on-demand
+---
+
+# harvest-loop — Detail Reference
+
+> Load when executing a specific step. SKILL.md contains operation modes, pipeline structure diagram, execution instructions overview, and Done When.
+
+---
+
+## §Step3-75 — Critic Isolated Agent Call
+
+```
+Agent(
+  prompt="Independently evaluate the following skill proposals.\n[synthesizer output passed]",
+  # synthesizer reasoning chain not inherited — blind evaluation
+)
+```
+
+Meaning of isolation: The Critic reads the synthesizer conclusion but does not inherit the reasoning chain that reached it (devil attack reflection/grade adjustment process). Independent reasoning path = resolves Cost of Consensus.
+
+**Evaluation items**:
+
+| Item | Judgment criteria |
+|---|---|
+| Done When logic validation | When condition is met, is the goal actually achieved? Is it measurable? |
+| Failure mode exploration | 2+ edge cases where this skill could fail |
+| Claim vs. implementation alignment | Does description promise contradict execution guide? |
+| Scope appropriateness | Too Narrow / Too Broad verdict |
+
+**FAIL routing** (infinite loop prevention):
+- First FAIL → pass Critic findings to synthesizer for **1 re-synthesis** allowed
+- FAIL after re-synthesis → auto-persist as `fh_signal` on hold (no additional retries)
+- Maximum retries: **1**
+
+**Post-Core-Skill Critic Verdict Connection**: Following core skills can have Critic called inline after completion: harness-doctor · verify-bidirectional · hub-cc-pr-reviewer · context-doctor · sim-conductor. Trigger: immediately after completion announcement + "steel-quench" / "re-validate" / "run Critic" utterance.
+
+---
+
+## §Step3-5X — Cross-Session 2nd Validation Bash
+
+```bash
+# Option A: External CLI team (if available — same detection as steel-quench Wave 5)
+SYNTH_CHALLENGE=$(printf \
+  'You are an adversarial reviewer with zero prior context.\nEvaluate these skill proposals and find flaws in the synthesis logic.\nFlag any HIGH-grade items that are over-promoted.\nFormat: [item · flaw · downgrade-to]\n---\n%s' \
+  "${SYNTHESIZER_OUTPUT}" | gemini 2>/dev/null)
+
+# Option B: Cross-session Claude (fallback)
+SYNTH_CHALLENGE=$(claude --print \
+  "Adversarial reviewer, zero context. Evaluate these skill proposals.
+Flag over-promoted HIGH-grade items. Format: [item · flaw · downgrade-to]
+---
+${SYNTHESIZER_OUTPUT}" 2>/dev/null)
+```
+
+**Outcome**:
+- Items flagged as over-promoted → downgrade HIGH → MED, proceed with caution
+- Confirmed across both → HIGH-confirmed → pass to Step 3.75 with elevated confidence
+- Zero new issues → synthesis confirmed, proceed normally
+
+Token cost: External CLI ~1K–2K tokens (billed to that CLI). Cross-session Claude ~2K–3K. Propose once — user may skip.
+
+---
+
+## §Step6-Detail — Bash Scripts for Curator + Memory + Leaderboard
+
+### 6-1. SKILL.md Lifecycle (bash)
+
+```bash
+# Detect skills unused for 30+ days (based on git log)
+git log --since="30 days ago" --name-only --pretty=format: \
+  plugins/*/skills/*/SKILL.md | sort -u > /tmp/recently_touched.txt
+
+find plugins -name "SKILL.md" | while read f; do
+  grep -qxF "$f" /tmp/recently_touched.txt || echo "[STALE candidate] $f"
+done
+```
+
+| Status | Judgment criteria | Action |
+|---|---|---|
+| **STALE** | 30+ day git no-modify + no recent session mention | Confirm with user, then mark `status: stale` in frontmatter |
+| **Pin protected** | `pinned: true` in frontmatter | Never touch under any circumstances |
+| **Merge candidate** | Two skills with ≥70% functional overlap | Suggest merge draft (no auto-execution) |
+| **Normal** | None of the above | Keep |
+
+### 6-2. Memory Self-Correction (bash)
+
+**Theoretical basis — Agent Aging 4 Mechanisms** (arXiv:2605.26302, AgingBench):
+
+| Aging type | Definition | 6-2 defense |
+|---|---|---|
+| **Compression aging** | Information loss during history compression | harvest-loop Step 0-a/b real-time recording obligation |
+| **Interference aging** | New knowledge corrupts existing | FILE-ORPHAN detection |
+| **Revision aging** | Stale facts after updates create inconsistency | MEM-STALE detection |
+| **Maintenance aging** | Side effects from routine cleanup | Curator safety principles — no auto-delete |
+
+```bash
+# MEMORY.md index vs actual files consistency check
+grep -oP '\[.*?\]\(\K[^)]+' memory/MEMORY.md | while read f; do
+  [ -f "memory/$f" ] || echo "[INDEX-ORPHAN] memory/$f — in index but file missing"
+done
+
+# Detect orphan files not in index
+find memory -name "*.md" ! -name "MEMORY.md" | while read f; do
+  fname=$(basename "$f")
+  grep -q "$fname" memory/MEMORY.md || echo "[FILE-ORPHAN] $f — file exists but not indexed"
+done
+
+# Detect memory files unmodified for 30+ days
+git log --since="30 days ago" --name-only --pretty=format: -- memory/ \
+  | sort -u > /tmp/recently_touched_mem.txt
+
+find memory -name "*.md" ! -name "MEMORY.md" | while read f; do
+  grep -qxF "$f" /tmp/recently_touched_mem.txt || echo "[MEM-STALE candidate] $f"
+done
+```
+
+| Status | Judgment | Action |
+|---|---|---|
+| **INDEX-ORPHAN** | In MEMORY.md but file missing | Remove from MEMORY.md immediately (auto-allowed) |
+| **FILE-ORPHAN** | File exists but not indexed | Confirm: "add to index or delete?" |
+| **MEM-STALE** | 30+ day git no-modify | Confirm: "archive or delete?" |
+| **PROJECT type priority** | `type: project` file | Suggest moving to CLOSED section if completed |
+
+Memory curator safety: Only INDEX-ORPHAN removal is auto-allowed. `type: reference` items with 🔑 keywords excluded from STALE detection.
+
+### 6-a. Skill Usage Leaderboard (bash)
+
+```bash
+# Check whether skill_usage.md exists
+ls tracks/_meta/skill_usage.md 2>/dev/null || echo "MISSING"
+```
+
+**If absent**: `cp {FH_DIR}/templates/skill_usage_template.md tracks/_meta/skill_usage.md`
+**If present**: Add row at bottom of "Recent session records" table:
+```markdown
+| {YYYY-MM-DD} | {comma-separated list of skills called this session} |
+```
+
+Update `Last used` date for called skills in Leaderboard table.
+Flag skills with 4+ weeks no call: status `⚠️ Under observation` → if 28+ days → `❌ Deprecation candidate`.
+
+### 6-b. Harness Evolution Cadence (bash — run when 4+ weeks of data accumulated)
+
+```bash
+# 1. Scan skills with complexity_routing
+grep -rl "complexity_routing" plugins/*/skills/*/SKILL.md
+
+# 2. Aggregate escalation records from fh_signal files
+grep -rh "" tracks/_meta/fh_signal_*.md 2>/dev/null | \
+  grep -oE "(harness-doctor|verify-bidirectional|hub-cc-pr-reviewer|context-doctor|sim-conductor|agent-composer|harvest-loop|steel-quench)" | \
+  sort | uniq -c | sort -rn
+```
+
+| Status | Criteria | Action |
+|---|---|---|
+| **Valid** | 1+ actual activations within last cycle | Keep |
+| **Removal candidate** | Never activated + 4+ weeks | Suggest removal |
+| **New candidate** | Pattern appearing repeatedly in fh_signal | Suggest addition |
+
+Output update candidate list → modify relevant SKILL.md after user approval. No auto-modification.
+
+---
+
+## §Observability — Full Observability Hook Spec
+
+> Frontier basis: `harness_frontier_diagnosis_2026-06-02.md` §Frontier Highlights 3 (AHE — agents cannot reliably improve a black-box harness).
+
+Every evolution decision must leave a 3-part trace in `tracks/_meta/edit_manifest.yaml`:
+
+| Trace part | Where | When written |
+|---|---|---|
+| **(a) what changed** | `edit_manifest.yaml` entry (file + diff summary) | On accepting a proposal (Y gate) |
+| **(b) predicted effect** | same entry's `predicted_impact` + `predicted_measurable_by` | Same moment — decision with no prediction is blind |
+| **(c) verify checkpoint** | same entry's `validation_status` (accepted/rejected) | Next harvest-loop Step 0-c VERIFY |
+
+**Decision-log obligation**: When Y gate accepts a proposal, append (a)+(b) pair to `edit_manifest.yaml` in the same step — do not defer. A proposal accepted without a recorded prediction is a black-box edit — flag, not silently applied.
+
+**Glass-box Done When**: harvest-loop should be able to answer "for each change, what did we predict and did it hold?" purely from `edit_manifest.yaml` — zero reliance on session memory.
+
+---
+
+## §Output-Detail — Session Card Update (Natural Language Close Judgment)
+
+**Natural-language close judgment (4th source — conversation context)**:
+
+Even without git log match, items with the following patterns stated in session are treated as "natural-language closed" and removed immediately:
+- "not possible / confirmed impossible" (endorsement not possible, cannot proceed)
+- "no response + N weeks elapsed" → abandoned
+- "mutual citation confirmed" · "merged" · "cancelled" · "no longer needed"
+- User directly says "stop monitoring" · "close this" · "remove it"
+
+Natural-language closed items → remove from card immediately (leave only "✅ closed" one-liner in reference table). Do not re-mention.
+
+**When fh_completed file is absent (2-source mode)**:
+- Source: starter card + git log only
+- Items confirmed by git log alone → "confirmed removal"
+- Card item name ↔ commit message mismatch → "removal candidate (uncertain)" + "real-time log missing — manual check needed: [item list]"
+- Exact match required — no LLM semantic judgment for "confirmed" status

package/plugins/fh-meta/skills/hub-cc-pr-reviewer/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: hub-cc-pr-reviewer
+description: Checks a submitted PR against the environment's baseline assets (CLAUDE.md, memory, naming, asset classification) and attaches a review comment with a merge recommendation. 5 steps — diff read, 8-area consistency check, self-catch, comment, merge recommendation.
+user-invocable: true
+allowed-tools: ["Bash", "Read", "Grep", "Glob"]
+model: sonnet
+complexity_routing:
+  base: sonnet
+  high: opus
+  escalate_when:
+    - adversarial
+    - cross_project
+    - high_stakes
+---
+
+> **Note:** The original developer is the forge-harness original developer (development source + meta-monitoring home). In external user install environments, the install environment user themselves is the baseline integrity gate operator (following path B generalization baseline / `SKILL_detail.md §External User Environment Adaptation Path` §).
+
+# hub-cc-pr-reviewer — Hub Gate Operation Rule Automation
+
+When a PR is submitted, checks consistency against the user environment's baseline assets (CLAUDE.md · memory · naming · asset classification) and attaches a review comment. 5-step: diff read → 8-matrix check → self-catch → comment attachment → merge recommendation.
+
+## Activation Triggers
+
+1. **PR #N input**: *"Review PR #N"* / *"Check PR #N"* / *"hub review"* / *"baseline consistency check"*
+2. **Action leader cc → hub sync point**: Large decision area PR catch (following Option C Hybrid policy — memory creation / CLAUDE.md change / CATALOG round / skill v0.x evolution / policy change / asset synergy branch judgment)
+3. **Hub cc session entry**: Layer A auto-read recent external commit catch (auto-discover new PRs)
+
+### Natural Language Triggers (General user phrasing — activates without internal vocabulary)
+
+| Example phrasing | Intent |
+|---|---|
+| "Is it okay to submit this PR?" | PR review request |
+| "This change seems inconsistent with existing rules" | Baseline consistency check |
+| "Please review before merging" | PR review gate |
+| "Does this change affect other parts?" | Consistency check |
+
+**Activation criteria**: "Review PR #N" / "Add review comment" / "Baseline check" → Run this skill directly  
+*(pr-review-watcher deprecated as of v0.2.0 — recommend using `gh pr view --json reviews` directly)*
+
+**Exceptions** (this skill does NOT apply):
+- **Small patches** (typo / 1-line cross-ref addition / sync / minor adjustments) → Follow Option C Hybrid policy (direct push allowed area / review skip)
+- **Original developer simple correction commands** ("This is wrong, redo it") → Immediate correction (no review / direct handling)
+
+## Processing Steps (5-step)
+
+### Step 1. PR Diff Read
+
+Read the PR diff + metadata. If this cc authored the change, the diff read can be skipped (directly state changed areas in PR body).
+
+> **Detail**: See `SKILL_detail.md §Step 1 Diff Read` — `gh pr diff` + `gh pr view` commands — read when executing the diff read.
+
+### Step 2. Baseline Consistency Check — 8-Matrix Auto-Generation
+
+| # | Area | Check path |
+|:---:|---|---|
+| 1 | CLAUDE.md (hub identity + asset ownership + sync policy) | Grep PR diff vs CLAUDE.md baseline areas |
+| 2 | Memory accumulation (accumulated naming/decision baseline + asset synergy branch judgment + active onboarding + bidirectional self-validation, etc.) | Grep PR diff vs `memory feedback_*.md` key areas (**External environment**: skip this item if memory files absent → `SKILL_detail.md §External User Environment Adaptation Path` §) |
+| 3 | Naming baseline (accumulated naming baseline + new naming candidate area) | Catch new naming candidates from PR diff / check adherence to existing naming |
+| 4 | Asset synergy branch judgment (meta/hub seed vs action leader persistent location) | Check PR changed asset location consistency |
+| 5 | Simplification guard (P15 asymmetry catch + R7 over-engineering) | New asset creation vs existing asset reinforcement judgment / body length check |
+| 6 | Dimension separation baseline (## Plugins / ## Skills / ## Agents) | Check dimension separation consistency on CATALOG changes |
+| 7 | Branch criteria (large decision PR mandatory vs small patch direct push) | Check if PR is a large decision area (Option C Hybrid) |
+| 8 | Hub gate operation consistency | Check if PR itself is a hub gate operation proof path |
+
+Matrix result = Consistent ✅ / Partially Consistent ⚠️ / Inconsistent ❌.
+
+### Step 3. Layer 5 Self-Catch Matrix
+
+Self-precision catch areas after first cc review (following previous PR self-catch patterns):
+- Check adherence to frontmatter description plain text only baseline (project baseline)
+- Check honest documentation of generalization effect weakening areas
+- Check explicit statement of gap between accumulated history (original developer environment) vs external user starting point (0 instances)
+- Check explicit statement that audience-specific guides are limited to original developer environment
+- Check explicit statement of organization-specific areas
+
+Self-catch areas 0 items = skip this entire catch matrix (no token-filling / following `feedback_simplification_evidence`).
+
+### Step 4. Review Comment Attachment
+
+Attach the review comment (8-matrix results + self-catch + refinement suggestions + merge recommendation) via `gh pr comment`. Within this skill's execution authority (automatic).
+
+> **Detail**: See `SKILL_detail.md §Step 4 Comment Template` — `gh pr comment` heredoc template — read when attaching the comment.
+
+### Step 5. Admin Override Merge Recommendation
+
+**User decision delegation** (this skill = review/recording automation / no merge authority):
+- Beta stage policy (`enforce_admins: false`) adherence → admin override possible
+- Self-approve blocked (GHE policy) → admin override path adherence
+- When this cc authored the change, admin override path is mandatory
+- N+1th operation proof = baseline stabilization acceleration path
+
+> **Detail**: See `SKILL_detail.md §Step 5 Merge Command` — `gh pr merge` command (executed after user decision, not by this skill) — read when the user authorizes merge.
+
+## User Approval Gate
+
+| Stage | Approval |
+|---|---|
+| Step 1~3 check auto-activation | **Automatic** (editable afterward) |
+| Step 4 review comment attachment | **Automatic** (gh pr comment within this skill's execution authority) |
+| Step 5 admin override merge execution | **User decision** (this skill = recommendation only / no merge authority) |
+
+## Constraints
+
+- **This skill = review/recording automation / no merge authority** — user admin override or other reviewer merge decision
+- **No single-person decision application** — following `fact-checker` rule (narrow 1 / broad N+1 / this cc self-catch joins fact-checker count)
+- **Simplification guard consistency** (`feedback_simplification_evidence`) — when creating/modifying this skill, update SKILL.md only. No new auxiliary files
+- **Markdown editing discipline mandatory** (`feedback_markdown_edit_discipline`) — Edit first. No Write
+- **Frontmatter description plain text only baseline** (`feedback_skill_frontmatter_description_plain_text`) — avoid markdown bold
+
+> **Detail**: See `SKILL_detail.md §Sister Asset Utilization Path`, `§External User Environment Adaptation Path`, `§Disable Path`, `§Persona Synergy Catch` — cross-ecosystem utilization, external-environment fallback, own-PRS disable resolution, and deep-insight simultaneous-activation handling — read when operating in an external user environment, resolving own-PRS conflict, or coordinating with deep-insight.
+
+## Done When
+
+```
+All 5 Steps completed
++ Baseline consistency check 8-matrix results output (✅/⚠️/❌ each item)
++ Review comment attached via gh pr comment command
++ Admin override merge recommendation output (merge execution is user's decision)
++ External verification path: harvest-loop Step 3.75 Critic isolation Agent can independently judge based on above criteria (skill_quality_rubric.md verifiable criteria)
+```
+
+**→ Mandatory when PR contains SKILL.md / rules / templates changes: `bash templates/regression_guard.sh`** — run Axis 1 (backward check) before merge recommendation is issued. If regression_guard exits with M-tier block, merge recommendation must change to ❌ regardless of other checks.
+
+## References
+
+- Rule body: `memory feedback_command_tower_gate.md` (hub gate accumulated naming baseline) + `memory feedback_qasp_to_hub_sync_protocol.md` (Option C Hybrid sync policy)
+- Consistency rules: `feedback_simplification_evidence` · `feedback_markdown_edit_discipline` · `feedback_skill_frontmatter_description_plain_text` · `feedback_bidirectional_self_validation` · `feedback_reference_own_hub_assets_first`
+- Sister skills: `cross-ecosystem-synergy-detection` (sister asset cluster baseline) · `verify-bidirectional` (bidirectional self-validation automation / self-catch auxiliary axis) · `harvest-loop` (weekly audit automation / operation proof accumulation cross-link)
+- Autonomous commit proposal §2.19 baseline: `memory feedback_autonomous_commit_proposal.md` (① development source automation + PR proposal under human approval)