tomevault-io Receive Feedback
Overview
Process code review feedback with verification-first discipline. No performative agreement. Technical correctness over social comfort.
Quick Reference
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ VERIFY │ ──▶ │ EVALUATE │ ──▶ │ EXECUTE │
│ (tool-based)│ │ (decision │ │ (implement/ │
│ │ │ matrix) │ │ reject/ │
└─────────────┘ └──────────────┘ │ defer) │
└─────────────┘
Core Principle
Verify before implementing. Ask before assuming.
When To Use
- Receiving code review from another LLM session
- Processing PR review comments
- Evaluating CI/linter feedback
- Handling suggestions from pair programming
Workflow
For each feedback item:
- Verify - Use tools to check if feedback is technically valid
- Evaluate - Apply decision matrix to determine action
- Execute - Implement, reject with evidence, or defer
Command Workflow
Use this skill from the /receive-feedback command or by invoking it directly with a feedback file path.
- Read the feedback file at
$ARGUMENTS - Parse individual feedback items, whether numbered, bulleted, or freeform
- Load this skill:
Skill(skill: "beagle-core:receive-feedback") - Process each item through verify → evaluate → execute
- Produce the structured response summary defined in
RESPONSE.md
Expected Feedback File Format
The feedback file may contain numbered or bulleted items:
1. Remove unused import on line 15
2. Add error handling to the API call
3. Consider using a generator for large datasets
4. Fix typo in variable name: `usr` → `user`
Freeform prose is also acceptable; extract actionable items from the text.
Example
/receive-feedback reviews/pr-123-feedback.md
Reads the file, processes each item with technical verification, and outputs a structured response table.
Files
VERIFICATION.md- Tool-based verification workflowEVALUATION.md- Decision matrix and rulesRESPONSE.md- Structured output formatreferences/skill-integration.md- Using with code-review skills
Converted and distributed by TomeVault — claim your Tome and manage your conversions.