void-learn

Capture recurring lessons and route them to project doctrine files or GitHub issues.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-learn-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-learn
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-learn
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-learn-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lessons learned during coding sessions evaporate between sessions: stated project rules get forgotten, recurring fixes are re-solved from scratch, and harness gaps go unreported. This Skill captures each lesson the moment it appears and routes it to the right destination under strict human-in-the-loop control. ## Core Features & Use Cases - Signal recognition and routing: Detects stated rules, deja-vu fixes, end-of-cycle patterns, and harness gaps, then decides whether the lesson belongs in .void/PROJECT-DOCTRINE.md, a GitHub issue on the harness repository, or nowhere. - HITL doctrine capture: Proposes rule wording, section placement, and enforcement mechanism in chat, and writes to PROJECT-DOCTRINE.md only after an explicit yes, with duplicate and conflict handling. - Harness feedback filing: Drafts and files gh issue create reports for harness gaps that pass an agnostic and harness-worthy bar, including source-project context. - Use Case: After merging a bugfix, you notice you solved the same null-dereference pattern twice. The Skill names the general pattern, asks whether it is project-specific or universal, and on your confirmation appends it to the doctrine so it applies from the next message. ## Quick Start Ask the agent to capture the rule you just stated and save it to the project doctrine after confirming the wording.

Frequently Asked Questions about void-learn

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

FAQPage Schema
How do I capture a project rule so the AI remembers it next session?

State the rule in conversation and the Skill proposes wording, a doctrine section, and an enforcement mechanism in chat. After you explicitly confirm, it appends the rule to .void/PROJECT-DOCTRINE.md, which is imported into every future session.

How do I report a missing skill or a false-positive hook in void-harness?

Describe the gap in plain language and the Skill drafts a GitHub issue with evidence and source-project context. After your confirmation it runs gh issue create against voidcorp-core/void-harness with the enhancement label.

Does the lesson capture write files automatically without asking?

No. The Skill is strictly human-in-the-loop: it never writes to PROJECT-DOCTRINE.md or creates an issue without an explicit yes. Silence, questions, or ambiguous replies stop the capture and trigger a re-ask.

When should a lesson be dropped instead of captured?

Drop lessons that are one-off occurrences, already covered by an existing skill or hook, impossible to state as a generalization, or that change no future behavior. Capturing trivial instances bloats the doctrine and dilutes its signal.

What happens if gh CLI is not installed or authenticated?

The Skill reports the missing or unauthenticated gh CLI and stops without filing the issue. It does not silently swallow the failure or fall back to another channel.