feedback-learning

Classify and record corrective feedback into authoritative repository artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users correct an AI agent's implementation or design choices, 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, such as a regression test, design document, instruction file, or learning inbox entry. - Learning Inbox Management: Maintains scoped .github/learnings/<area>.md files with strict size limits, compaction, and 90-day review cycles. - Deduplication Discipline: Searches existing rules before writing and removes inbox entries once promoted to authoritative documents. - Use Case: A reviewer rejects an agent's error-handling pattern in a pull request. The Skill determines the feedback is a concrete behavior that must not regress, encodes it as a regression test, and avoids adding a redundant rule to the instructions. ## Quick Start Record the user's correction about the retry logic in the API client 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 make an AI agent remember corrective feedback?▼

Classify the correction first: one-off preferences are not persisted, concrete behaviors become regression tests, and stable architecture rules go into design documents. Only reusable but unproven guidance goes into a scoped learning inbox file.

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

Store it in the smallest authoritative artifact: tests for behavior, design documents for architecture, instruction files for universal rules, and .github/learnings/<area>.md for immature guidance. Never duplicate the same rule across multiple destinations.

Does this skill handle the literal learn! trigger 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 corrections and feedback-learning requests.

What are the limits of a learning inbox file?▼

Each area inbox is limited to ten topics and 8 KB. Before adding an entry, the inbox must be compacted, and a full review is required when limits are reached or the Last reviewed date is over 90 days old.

When should feedback not be persisted at all?▼

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