Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

pull-feedback

Étoiles18

Forks0

Mis à jour10 juillet 2026 à 00:40

Pull and manage feedback from korulang.org. Use to see what users are reporting about tests/documentation, prioritize work, and mark items resolved.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

korulang

korulang/koru

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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.

Feedback Tool

Pull user feedback from korulang.org (stored in Convex) and manage it.

Commands

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

Workflow

Quick start for tonight's work:

Run --lowest to see the 5 lowest-rated pages with feedback
Pick a page, fix the issues
Re-rate the page on korulang.org after improving it

Finding best practices / gold standard examples:

Run --ratings to see all rated pages (highest first)
Run --ratings 5 to see only 5-star pages (curated examples)
Use these as templates when creating new tests or documentation

Full feedback workflow:

Run /pull-feedback to see open items
Use --context <id> to see the full test code for an item
Either:
- Fix the issue directly, then --done <id>
- Use --priority <id> to create a PRIORITY file in the test dir (auto-closes feedback)
Delete PRIORITY file when the work is complete

Notes

IDs are 8-character prefixes of the full Convex ID
Prioritized items (P1) appear first in the list
Feedback is URL-anchored to specific pages on korulang.org
The --priority command maps URLs back to test directories in this repo

Requirements

~/src/korulang_org/.env.local must contain:
- PUBLIC_CONVEX_URL - Convex deployment URL
- ADMIN_SECRET - Required for mutations (done/wontfix/reopen)

Plus depuis ce dépôt

même dépôt

membrane

korulang/koru

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.

2026-07-2618

koru-metaprogramming

korulang/koru

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.

2026-07-2618

koru-templates

korulang/koru

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.

2026-07-2618

koru-toolchain

korulang/koru

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.

2026-07-2518

regression

korulang/koru

Koru regression test harness workflow. Use when checking test status, investigating failures, or coordinating test runs with the user.

Feedback Tool

Pull user feedback from korulang.org (stored in Convex) and manage it.

Commands

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

Workflow

Quick start for tonight's work:

Run --lowest to see the 5 lowest-rated pages with feedback

Pick a page, fix the issues

Re-rate the page on korulang.org after improving it

Finding best practices / gold standard examples:

Run --ratings to see all rated pages (highest first)

Run --ratings 5 to see only 5-star pages (curated examples)

Use these as templates when creating new tests or documentation

Full feedback workflow:

Run /pull-feedback to see open items

Use --context <id> to see the full test code for an item

Either:

Fix the issue directly, then --done <id>
Use --priority <id> to create a PRIORITY file in the test dir (auto-closes feedback)

Delete PRIORITY file when the work is complete

Notes

IDs are 8-character prefixes of the full Convex ID

Prioritized items (P1) appear first in the list

Feedback is URL-anchored to specific pages on korulang.org

The --priority command maps URLs back to test directories in this repo

Requirements

~/src/korulang_org/.env.local must contain:

PUBLIC_CONVEX_URL - Convex deployment URL
ADMIN_SECRET - Required for mutations (done/wontfix/reopen)