القائمة
Pull and manage feedback from korulang.org. Use to see what users are reporting about tests/documentation, prioritize work, and mark items resolved.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Tend the membrane memory corpus — an OKF concept store whose fragment evolution lives in the git log as lineage trailers. Fire when creating, evolving, merging, splitting, or CORRECTING durable memory/knowledge that lives as OKF files under git; when recording how a belief changed or was repudiated; or when tracing a concept's history through time. YOU are the evolver — there is no evolution engine and no LLM sidecar. NOT for transient notes, scratch, or code comments.
Compile-time metaprogramming in Koru: event globbing and compile-time event matching — the "you are the compiler" surface where userland code sits inside the pipeline. Use when writing compile-time event selection or pattern-matching over events. SEED TOPIC — currently scoped to event globbing; widen `clusters` in koru-by-example.json as the metaprogramming surface grows.
Control flow in Koru: `~if` and `~for` as templates over continuation-return, not host keywords. Use when emitting conditionals or iteration in Koru, or when working on the template/lowering layer (`koru_std/control.kz`). Covers how `for`/`if` select continuations and lower per target.
How to work with the Koru language and its compiler `koruc`. Use when working in a Koru repo (`.kz`/`.k` files), running or reading regression tests, or when you need to orient on the toolchain — what the language is called, how to compile, where the docs and tests live. Start here before reading code.
Koru regression test harness workflow. Use when checking test status, investigating failures, or coordinating test runs with the user.
How to work with the Koru language and its compiler `koruc`. Use when working in a Koru repo (`.kz`/`.k` files), running or reading regression tests, or when you need to orient on the toolchain — what the language is called, how to compile, where the docs and tests live. Start here before reading code.
| name | pull-feedback |
| description | Pull and manage feedback from korulang.org. Use to see what users are reporting about tests/documentation, prioritize work, and mark items resolved. |
Pull user feedback from korulang.org (stored in Convex) and manage it.
Run from the korulang_org directory:
cd ~/src/korulang_org
# List all open feedback (default)
node scripts/pull-feedback.js
# View a specific item (use 8-char ID prefix)
node scripts/pull-feedback.js abc12345
# View with full test context (code + expected output)
node scripts/pull-feedback.js --context abc12345
# Mark as resolved
node scripts/pull-feedback.js --done abc12345
# Mark as won't fix
node scripts/pull-feedback.js --wontfix abc12345
# Reopen a closed item
node scripts/pull-feedback.js --reopen abc12345
# Create PRIORITY file in the test directory from feedback
node scripts/pull-feedback.js --priority abc12345
# Filter by category
node scripts/pull-feedback.js --category 310-comptime
# Full JSON dump
node scripts/pull-feedback.js --json
# Tonight's work: 5 lowest-rated pages with feedback
node scripts/pull-feedback.js --lowest
# List all rated pages (high to low)
node scripts/pull-feedback.js --ratings
# List rated pages (low to high)
node scripts/pull-feedback.js --ratings --low
# List pages with specific rating (1-5)
node scripts/pull-feedback.js --ratings 1
node scripts/pull-feedback.js --ratings 5
Quick start for tonight's work:
--lowest to see the 5 lowest-rated pages with feedbackFinding best practices / gold standard examples:
--ratings to see all rated pages (highest first)--ratings 5 to see only 5-star pages (curated examples)Full feedback workflow:
/pull-feedback to see open items--context <id> to see the full test code for an item--done <id>--priority <id> to create a PRIORITY file in the test dir (auto-closes feedback)--priority command maps URLs back to test directories in this repo~/src/korulang_org/.env.local must contain:
PUBLIC_CONVEX_URL - Convex deployment URLADMIN_SECRET - Required for mutations (done/wontfix/reopen)