claudeframework: Skill for Claude Code

Apply accepted proposals from .claude/reviews/learn-proposals.md to the target skill and rule files.

$ARGUMENTS is optional:

• --all — apply all proposals with Status accepted
• --proposal <N> — apply only proposal number N (by order of appearance), regardless of Status
• No arguments — interactive mode: present pending proposals for review, then apply accepted ones

Step 0 — Load proposals

1. Read .claude/reviews/learn-proposals.md. If the file doesn't exist, report "No proposals file found. Run /scout or /learn first." and stop.
2. Parse each proposal block. A proposal starts with ### Skill: or ### New skill: or ### Rule: and contains:
   • **What:** — one-line description
   • **Why:** — motivation
   • **Source:** or **Source tier:** — provenance
   • **Status:** — pending / accepted / rejected / deferred
   • **Diff:** — the proposed change (old → new)
3. Build a numbered list of all proposals with their Status.

Step 1 — Select proposals to apply

If --all: select every proposal with Status accepted.

If --proposal <N>: select only that proposal. If its Status is not accepted, ask: "Proposal #N has status <status>. Apply anyway? (Y/N)" — proceed only if Y.

If no arguments (interactive mode):

1. Print all proposals in a numbered table:

   | #  | Target            | What                          | Status   | Tier |
   | -- | ----------------- | ----------------------------- | -------- | ---- |
   | 1  | /2_review         | Add disallowedTools           | pending  | T1   |
   | 2  | /3_fix            | Add maxTurns: 15              | pending  | T1   |
   

2. Ask: "Which proposals to apply? Enter numbers (e.g. 1,3,5), all for all pending, or q to quit."
3. For each selected proposal, update its Status to accepted in learn-proposals.md before applying.

If no proposals are selected (or all are already accepted/rejected), report and stop.

Step 2 — Validate diffs before applying