skills.rest
e-stpierre
e-stpierreCOMMUNITY
Explore all skills by this author →
GitHub

af-analyze

Analyze codebases for bugs, debt, documentation, security, and style issues.

1|Updated Nov 12, 2025
Search Tags:#consistency#codebase#static-analysis#analyze#json-output#markdown-report#issue-detection
One-click install
npx skills add https://github.com/e-stpierre/agentic-forge --skill af-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: af-analyze
Source: https://github.com/e-stpierre/agentic-forge/tree/main/src/claude/.claude/skills/analyze
Command: npx skills add https://github.com/e-stpierre/agentic-forge --skill af-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes a codebase to identify bugs, debt, documentation gaps, security risks, and style inconsistencies, returning structured findings for automation and reporting.

Core Features & Use Cases

  • Multi-domain analysis: detects issues across bugs, debt, docs, security, and style in a single pass.
  • Structured outputs: emits JSON findings for workflow integration and generates a Markdown report for human review.
  • Use Case: In a CI workflow, run this skill to surface actionable issues across a repository and generate a quick assessment report.

Quick Start

Run af-analyze on the repository root or specific paths to generate JSON findings and a Markdown report.

Frequently Asked Questions about af-analyze

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

FAQPage Schema
How do I run static analysis to detect bugs and code debt in a repository?▼

Run static analysis on a repository root or targeted paths to detect bugs, code debt, documentation gaps, and style issues in a single pass. The analysis outputs structured JSON findings for workflow integration and a Markdown report for human review.

What is codebase static analysis and how does it categorize code issues?▼

Codebase static analysis identifies and categorizes issues across bugs, debt, documentation, security, and style domains. It evaluates source code without execution to surface actionable findings for automation and reporting.

Can I use static analysis for targeted paths in a monorepo?▼

Yes, static analysis can be applied to monorepos and projects of varying sizes. You can analyze the entire codebase or target specific paths to isolate findings within distinct sections of a large repository.

Does codebase analysis output JSON for CI workflow integration?▼

Yes, codebase analysis produces a structured JSON findings payload designed for CI workflow integration. It also generates a Markdown report to provide a quick assessment for human review.

What is the best way to generate a markdown report for codebase security risks?▼

The best way to generate a markdown report for codebase security risks is to run a multi-domain static analysis pass. This identifies security vulnerabilities alongside bugs and debt, outputting both a structured JSON payload and a human-readable report.

Related Skills

Explore More Software Engineering Skills→
abatiloabatilo
10

repo-explore

Clone and analyze GitHub repositories with version-aware code exploration.

Community
Basic
semicolon-devteamsemicolon-devteam

iteration-tracker

Track test iterations and outcomes for GitHub issues via issue comments.

Official
Advanced
Patasse97Patasse97

report

Generate Markdown and HTML test reports from Playwright results.

Community
Intermediate
BrunoSantanaDeveloperBrunoSantanaDeveloper

parallel-agents

Coordinate multiple specialized agents for multi-domain tasks in a unified session.

Community
Advanced