lore

Capture and index architectural decisions via @lore annotations.

Updated Jun 12, 2026

Search Tags:#architecture #documentation #onboarding #knowledge management #codebase #technical debt

Ready to run

npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill lore-ambrovia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lore
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/lore
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill lore-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the loss of critical architectural decisions, constraints, and workarounds that often remain trapped in developers' heads or buried in old pull requests.

Core Features & Use Cases

Capture: Annotate code with @lore comments to document non-obvious constraints, cross-cutting decisions, and performance tradeoffs.
Scan: Automatically identify undocumented decisions or patterns that warrant formal documentation.
Index: Generate a searchable knowledge map of all documented lore across the entire codebase.
Use Case: When a developer wonders why a specific dependency is pinned or why a module cannot be merged, they can use the index to find the original decision context immediately.

Quick Start

Use the lore skill to scan the current directory for undocumented decisions that require annotation.

Frequently Asked Questions about lore

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

FAQPage Schema

How do I document architectural decisions and prevent knowledge loss in a codebase?▼

To prevent knowledge loss, capture cross-cutting architectural decisions and constraints by annotating code with inline comments. This documents workarounds and gotchas, ensuring critical context is retained rather than trapped in developer memory or old pull requests.

What is tribal knowledge in software engineering and how do you manage it?▼

Tribal knowledge consists of non-obvious constraints and performance tradeoffs known only to specific developers. Manage it by facilitating the formal documentation of these decisions through inline annotations and automated scanning, creating an auditable record across multiple modules.

How do I find out why a specific dependency is pinned or why a module cannot be merged?▼

To find the original decision context for pinned dependencies or unmergeable modules, generate a searchable knowledge map by indexing documented lore across the entire codebase. This enables immediate retrieval of the specific architectural constraints causing the issue.

How do I scan my codebase for undocumented architectural decisions?▼

Scan your current directory to automatically identify undocumented decisions or patterns that warrant formal documentation. This automated scanning highlights missing context and prompts developers to add necessary annotations for architectural constraints.

What is the best way to onboard developers to technical debt and cross-cutting codebase constraints?▼

The best way to onboard developers to technical debt is by providing a searchable index of architectural knowledge. Indexing documented lore across files allows new team members to retrieve historical decision context and understand non-obvious performance tradeoffs immediately.