learn

To verify codebase discoveries before updating project documentation, you can capture claims and cross-check them against files, configuration, and existing docs. The skill performs duplication checks, reads files to fact-check, and marks confidence levels before writing validated entries into a learn history file.

Documenting implicit business rules learned from customer patterns involves extracting core assertions, asking clarifying questions if details are missing, and rewriting them into precise knowledge. Validated rules are then proposed as updates to appropriate doc targets like business rules or module docs.

Fact-checking newly learned team conventions against existing code is done by applying duplication checks and searching the codebase. The skill reads relevant files to validate the claims, asks up to three follow-up questions if needed, and assigns a status of OK, FAIL, WARN, or undecided.

Yes, you can log validated development knowledge into a daily history file. Once a newly learned work fact is checked and concretized, the skill records the accumulated learn history entry under the .local.claude/learn/YYYY-MM-DD.md file path.

To prevent unverified claims from spreading in official documentation, validate discoveries by cross-checking user-provided claims against the codebase and configuration before writing them. The skill clarifies ambiguous inputs and marks confidence levels to ensure only reliable knowledge is documented.

Automated fact-checking for codebase rules is limited by the need for clarifying questions when details are missing. The skill asks up to three follow-up questions to concretize ambiguous inputs, but it cannot validate claims if the necessary source files or configuration data are inaccessible.