setup-audit

Audit a repository to extract architecture principles and generate .claude/references/architecture-principles.md.

6|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill setup-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-audit
Source: https://github.com/moberghr/mtk-agent-toolkit/tree/main/.claude/skills/setup-audit
Command: npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill setup-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill audits a repository to extract architecture principles and generate a reference document that describes the actual software architecture and organizational conventions observed in the codebase.

Core Features & Use Cases

  • Automated architectural audits: Detect and document architecture principles, patterns, and conventions present in the repository.
  • Merge-ready outputs: Produce per-repo architecture-principles.md and, with --merge, unify audits into a single reference document.
  • Guided workflow for engineers: Produce actionable guidance for teams to align practices and onboard new contributors.

Quick Start

Run the audit to generate architecture-principles from this repository.

Frequently Asked Questions about setup-audit

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

FAQPage Schema
How do I extract architecture principles and conventions from an existing codebase?

Extract architecture principles by running an automated audit over the repository to detect tech stack, file structure, patterns, and conventions. The audit generates a per-repo architecture-principles document describing the actual software architecture observed in the codebase.

Can I merge architecture audits from multiple repositories into a single reference document?

Merge architecture audits from multiple repositories by using the --merge workflow, which unifies individual per-repo audit outputs into a common reference document for cross-repo architectural alignment.

What is the best way to document software architecture patterns for onboarding new contributors?

Document software architecture patterns by auditing the repository to identify existing conventions and generate an architecture-principles.md reference, producing actionable guidance to align team practices and onboard new contributors.

Does the architecture audit require any external dependencies or environment setup?

The architecture audit requires no external dependencies or environment setup, running directly as an automated standalone process to analyze the codebase and produce reference files in the .claude/references directory.

When should I use a single-repo architecture audit instead of a multi-repo merge workflow?

Use a single-repo architecture audit to extract principles and conventions for one repository, and switch to the multi-repo --merge workflow when you need to unify separate audits into a common reference across multiple codebases.