skills.rest
SeoJaeWan
SeoJaeWanCOMMUNITY
Explore all skills by this author →
GitHub

review-wiki-ingest

Ingest review inbox markdown files into raw evidence records and registry-backed pattern rules.

1|Updated Mar 6, 2026
Search Tags:#planning#registry#wiki#reviews#ingest#pattern-rules
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill review-wiki-ingest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-wiki-ingest
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/.codex/skills/review-wiki-ingest
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill review-wiki-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codex review files from the main repository root under .codex/reviews/**/*.md are ingested into the user-level review wiki, enabling structured raw evidence and reusable planning rules.

Core Features & Use Cases

  • Ingests review inbox markdown files and normalizes them into integrated raw records.
  • Updates the wiki registry and pattern rules to reflect new planning insights for future architect and plan-review runs.
  • Ensures source reviews are batched and deleted only after successful ingestion.

Quick Start

Ingest the current inbox of reviews into the review wiki and registry to seed planning automation.

Frequently Asked Questions about review-wiki-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ingest markdown review files into a planning wiki registry?▼

It ingests markdown reviews by matching exact Branch headers to plans, normalizing files into raw evidence records, and updating `wiki/registry.json` with promoted pattern rules for future planning automation.

What happens to review inbox files after they are ingested into the registry?▼

Source reviews are batched and securely deleted only after successful ingestion ensures raw records are normalized and pattern rules are validated and promoted within the registry.

How does the wiki registry match ingested reviews to existing plans?▼

Reviews are matched to plans by exact Branch headers, aligning raw evidence with existing planning structures to update the wiki registry and promote pattern rules for architect runs.

Do I need a specific schema to validate review pattern rules for planning automation?▼

Yes, the review-wiki-ingest references and pattern schema are required to validate and promote pattern rules, ensuring ingested raw evidence correctly updates the registry for future architect and plan-review runs.

Why are my ingested reviews not updating the wiki registry pattern rules?▼

Wiki registry updates fail when review markdown files lack exact Branch headers matching existing plans, or if the pattern schema validation rejects the raw evidence before rules can be promoted.

Related Skills

Explore More Content & Communication Skills→
SpillwaveSolutionsSpillwaveSolutions
62

confluence

Convert Markdown to Confluence Wiki Markup and update pages via REST.

Official
Advanced
SeoJaeWanSeoJaeWan
1

review-wiki-lint

Audit review wiki registry and pattern files for drift and orphan registrations.

Community
Intermediate
2389-research2389-research
90

cookoff

Coordinate parallel implementation plans from a shared design.

Official
Advanced
netanel-abergelnetanel-abergel
5

self-learning

Log corrective events and extract behavioral patterns into actionable rules.

Community
Advanced