菜单
Use when you hit a gap, anti-pattern, bug, or missing guidance in rebar's templates, practices, or scripts during real work — or when the user says "file feedback" / "write this up for rebar." Files a durable feedback item instead of editing templates directly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when asked about a rebar repo's health, compliance, tier, or contract status — and before claiming any tier, badge, or "green" state in docs or commits. Runs the three status surfaces and reads them without conflating the two maturity vocabularies.
Use at the start of every session in a REBAR-managed repo, before the first substantive task — and any time you catch yourself working from stale context (post-compaction restart, missing cold-start hook output, QUICKCONTEXT claims that don't match git reality). Runs the session-start ritual that grounds you in current project state.
Use during multi-repo coordination phases (release days, cross-repo arcs, ratification rounds) when this repo holds a peer inbox/ directory — arms a persistent background watcher so new memo deposits reach you as live notifications instead of sitting unread while a peer waits.
| name | rebar-feedback |
| description | Use when you hit a gap, anti-pattern, bug, or missing guidance in rebar's templates, practices, or scripts during real work — or when the user says "file feedback" / "write this up for rebar." Files a durable feedback item instead of editing templates directly. |
Canonical reference: rebar:feedback/README (template, processing rules,
disposition lifecycle) — resolve with scripts/rebar-doc.sh rebar:feedback/README --cat (or rebar doc if the CLI is installed).
Reference it; do not restate it.
feedback/): file locally,
steps below.feedback/ directory): the feedback is
about rebar, so it belongs upstream — use ask rebar featurerequest "<the situation>" (MCP/ASK), or write the file into your rebar checkout's
feedback/ directory. Do not create a feedback/ dir in the adopter repo
for rebar-bound items.rebar:feedback/README, above) and skim
one recent feedback/*.md file for the house voice before writing anything.rebar:charter §3, gate 3: concrete use
case). "Would be cool if…" does not qualify; do not file.feedback/YYYY-MM-DD-<slug>.md (today's date, short
kebab-case slug).Date, Source, Type, Status
(start at proposed), Template impact, From (agent/model, project,
date — provenance matters).Do not edit feedback/INVENTORY.md or move files into feedback/processed/
— triage and disposition are maintainer-owned (see "Processing Feedback" in
rebar:feedback/README).