audit

Generate and gap-fill MEMORY.md context files that document a project's stack, commands, and conventions.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/idehen-divine/lumished --skill audit-idehen-divine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/idehen-divine/lumished/tree/main/.ai/skills/audit
Command: npx skills add https://github.com/idehen-divine/lumished --skill audit-idehen-divine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding agents and new team members lack durable project context: coding standards, stack decisions, daily commands, and area-specific conventions live nowhere or get lost. This Skill bootstraps that context by scanning a codebase (or asking on greenfield projects) and writing tool-agnostic MEMORY.md files that every later skill and AI tool reads. ## Core Features & Use Cases - Phase-based routing: Detects project state (greenfield, undocumented brownfield, partially documented, or single area) and runs the matching audit mode, including legacy context file migration with permission. - Root and nested context files: Writes a short global root MEMORY.md plus nested area MEMORY.md files only where distinct conventions warrant them, never overwriting curated content. - Greenfield standards capture: Asks coding standards questions (architecture style presets like Clean Architecture, DDD, Functional, SOLID OOP) and seeds root MEMORY.md from the architecture spec and scope header. - Use Case: After scaffolding a new Laravel or Next.js app, run the audit to record the stack, commands, and chosen conventions in MEMORY.md so every subsequent AI-assisted task follows them; later, run it on src/auth to document that area's gotchas. ## Quick Start Ask the agent to run the audit skill on this project to create the MEMORY.md context files, optionally passing an area path like src/auth to document just that module.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I create MEMORY.md context files for an existing codebase?▼

Run the audit skill with no arguments on a repo that has real code but no root MEMORY.md. It scans the project, extracts the stack, commands, and conventions, then writes a root MEMORY.md plus nested docs for areas that warrant them.

How to document coding standards for a new greenfield project?▼

Run the audit after scaffolding. It asks multiple choice questions about architecture style, type strictness, folder structure, and tooling, then seeds root MEMORY.md from your answers and the architecture spec's proposed stack.

Can I audit just one folder like src/auth instead of the whole repo?▼

Yes, pass an area path as an argument, such as /audit src/auth. The skill explores only that area, creates or updates its nested MEMORY.md, and flags any gaps the root file is missing.

Does the audit skill overwrite existing MEMORY.md files?▼

No. It never overwrites an existing MEMORY.md. It proposes additions through a diff format and asks permission before modifying root files or migrating legacy context files, treating human-edited content as curated.

Does the audit skill work with monorepos?▼

Yes. It detects workspace markers like pnpm-workspace.yaml or turbo.json, writes a root MEMORY.md for monorepo-wide concerns, and creates a light stub MEMORY.md per workspace from its manifest without deep scanning every package.

What are the limitations of the audit skill?▼

It does not create architecture specs, maintain files after code changes, or write feature scopes; those belong to other skills. It also flags contradictions between docs and code for a human to resolve rather than fixing them automatically.