feedback-learning

Classify and record corrective feedback into authoritative repository artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users correct an agent's implementation or design approach, that knowledge 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 or contradictory 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 including scope, evidence, and disposition. - Compaction and Garbage Collection: Promotes mature guidance into specifications, encodes behavior in tests, merges overlapping entries, and removes obsolete ones. - Use Case: A user rejects an error-handling pattern in a build subsystem. The skill checks existing instructions, generalizes the principle, and records it once in the relevant design document or learning inbox without duplicating it elsewhere. ## Quick Start Record the user's correction about the rejected retry pattern into the appropriate learning destination using the feedback-learning workflow.

Frequently Asked Questions about feedback-learning

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

FAQPage Schema
How do I record corrective feedback from a user in a repository?▼

Identify what was wrong and the preferred approach, search existing instructions and design documents for duplicates, then classify the feedback into the right destination such as a regression test, design document, or learning inbox entry.

Where should reusable agent feedback be stored?▼

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 scoped learning inbox files under .github/learnings.

When should user feedback not be persisted?▼

Task-specific preferences and one-off adjustments should not be persisted at all. A single rejected implementation should also not become a universal prohibition without broader supporting evidence.

What are the limits of a learning inbox file?▼

Each area inbox is limited to ten topics and 8 KB. Before adding an entry that would exceed either limit, existing entries must be promoted, merged, or removed through compaction.

Does this skill handle the literal learn! trigger?▼

No. Literal learn! requests are governed exclusively by the learnings instructions file and are outside this skill's scope. The skill covers all other explicit corrections and feedback-learning requests.