complexity-audit

Orchestrate four-phase complexity audits with issue creation, worktrees, and PR reporting.

17|1|Updated Nov 17, 2024
One-click install
npx skills add https://github.com/mifunedev/orchestra --skill complexity-audit-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complexity-audit
Source: https://github.com/mifunedev/orchestra/tree/main/.claude/skills/complexity-audit
Command: npx skills add https://github.com/mifunedev/orchestra --skill complexity-audit-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end complexity audits by coordinating issue creation, worktrees, and PR reporting for targeted code paths or glob patterns.

Core Features & Use Cases

  • Orchestrates four-phase audits: measure, identify patterns, benchmark, draft PR
  • Supports targets like backend/ or frontend/ and 'all', with optional existing GitHub issue
  • Delegates execution to the complexity-auditor agent and surfaces results in PR artifacts

Quick Start

Provide a TARGET path to audit (e.g., backend/src/services/ or all); the skill will orchestrate the full workflow and report results.

Frequently Asked Questions about complexity-audit

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

FAQPage Schema
How do I automate code complexity audits for targeted paths in Python or TypeScript projects?

Automate code complexity audits by providing a target path like backend/src/services/ or frontend/src/components/ to orchestrate issue creation, worktree setup, and PR reporting. The skill delegates execution to an auditor agent and stores artifacts under .audit/.

What does an end-to-end complexity audit workflow include?

An end-to-end complexity audit workflow includes four phases: measuring code complexity, identifying complexity patterns, benchmarking results, and drafting a reviewer-ready PR with audit artifacts stored in the .audit/ directory.

Can I run a complexity audit on my entire codebase or just specific directories?

You can run a complexity audit on your entire codebase by passing 'all' as the target, or scope it to specific directories like backend/ or frontend/ for both Python and TypeScript projects.

Do I need an existing GitHub issue to start a code complexity audit?

You do not need an existing GitHub issue to start a code complexity audit. The workflow supports optional existing GitHub issues and can orchestrate issue creation automatically as part of the audit setup.

What's the best way to report code complexity findings to reviewers?

The best way to report code complexity findings is through reviewer-ready PRs generated by the audit workflow. The skill orchestrates git worktree setup and surfaces audit results directly in PR artifacts for easy reviewer access.

Why should I use git worktrees when auditing code complexity?

Git worktrees isolate complexity audit changes from your main branch, allowing the auditor agent to measure code, identify patterns, and draft PRs in a dedicated workspace without disrupting ongoing development.