feedback-learning

Classify and record corrective user feedback into authoritative repository artifacts.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill feedback-learning-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-learning
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/feedback-learning
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill feedback-learning-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users correct an AI agent's implementation or design choices, that feedback is often lost or dumped into ever-growing instruction files. This Skill ensures each correction is classified and stored once in the smallest authoritative artifact, preventing duplicated, contradictory, or bloated guidance. ## Core Features & Use Cases - Feedback Classification: Routes each correction to the right destination—regression test, design document, instruction file, learning inbox, or no persistence at all. - Learning Inbox Management: Maintains scoped .github/learnings/<area>.md files with strict limits (ten topics, 8 KB) and a defined entry format. - Compaction and Garbage Collection: Promotes mature guidance into specifications, encodes behavior in tests, and removes obsolete or contradicted entries. - Use Case: A user rejects an error-handling pattern in the agent host. The Skill checks existing instructions, generalizes the principle, and records it once in the relevant design document instead of scattering copies across files. ## Quick Start Ask the agent to record the correction you just made using the feedback-learning workflow so it is stored in the right place.

Frequently Asked Questions about feedback-learning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent remember my corrections?▼

Invoke the feedback-learning workflow when you correct an implementation or design approach. The Skill classifies the feedback and records it once in the appropriate destination, such as a regression test, design document, instruction file, or scoped learning inbox.

Where should reusable coding feedback be stored in a repository?▼

Storage depends on the feedback type: concrete behavior goes into regression tests, stable architecture into design documents, universal rules into instruction files, and immature guidance into .github/learnings/<area>.md inbox files. One-off preferences are not persisted.

Does this skill handle the learn! command?▼

No. Literal learn! requests are governed exclusively by .github/instructions/learnings.instructions.md and are outside this skill's scope. This skill covers all other explicit corrective feedback.

What are the limits of learning inbox files?▼

Each area inbox is limited to ten topics and 8 KB. Before adding an entry, the inbox is compacted; entries older than 90 days or exceeding limits trigger a full review that promotes, merges, or removes entries.

When should feedback not be persisted as a rule?▼

Task-specific preferences and one-off adjustments should not be persisted. A single rejected implementation should not become a universal prohibition without broader evidence, and temporary details like line numbers should be excluded.