Results for “analysis”

Enforces complexity analysis, correct data structure selection, vectorization, and algorithm implementation discipline at principal-engineer level.

Measures code quality, identifies code smells, and implements quality gates using static analysis and technical debt tracking.

Analyzes code for logical errors, race conditions, security vulnerabilities, and algorithmic flaws using structured reasoning across 9 risk categories.

Extracts specifications from existing codebases by analyzing structure, data flows, and observable behaviors to document requirements in EARS format.

Performs structured code reviews of git branches, tracking findings in a living document and optionally running deep architectural analysis with subagents.

Enforces an algorithm-first discipline: state Big-O, data structure, and algorithm family before writing loops, queries, or recursion to catch O(n²), N+1, and brute-force defaults.

Explora el código y el dominio del problema antes de proponer un cambio, documentando hallazgos y recomendaciones.

Forces investigation of file dependencies before editing code to prevent cascade failures.

Analyzes codebases to map entry points, execution flows, architecture layers, patterns, and dependencies before new development begins.

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Answers questions about a codebase by searching and reading source files, then synthesizing answers with inline citations and a key files table.

Answers questions about a code repository by searching and reading source files, then synthesizing answers with inline citations and a key files table.

Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

Mines git history and codebase to reconstruct the development lifecycle, identify sequential and parallel patterns, and produce actionable recommendations for future iterations.

Provides shared C language infrastructure for OpenClaw skills, including AST parsing, CMake analysis, Unity test generation, and security rule checking.

Analyzes codebases to understand existing features, tracing entry points, execution paths, architecture layers, patterns, and dependencies before new development.

Provides a CTO-level framework for architecting, auditing, and scaling AI-native systems, focusing on state management, observability, and blast radius analysis.

Scan C# source files for hard-to-test static dependencies and produce a ranked report of static call sites by frequency.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

Review, triage, validate, and discuss ClawHub GitHub issues and pull requests with structured evidence, best-fix analysis, and maintainer handoff.

Scans a codebase for Martin Fowler's catalog of code smells, reporting each with location, severity, and refactoring recommendations, and ranks files to build a prioritized refactoring queue.

Reviews code through the lens of 12 classic software engineering books, catching design smells, coupling issues, and architectural risks that linters miss.

Scans Python and JavaScript codebases for bugs, security vulnerabilities, code smells, and anti-patterns, producing a prioritized fix list with line numbers, severity ratings, and suggested corrections.

Mines a codebase for evidence-backed improvement opportunities, forcing two escalation gates to surface breakthrough ideas, and outputs a ranked portfolio with a plan seed without implementing.

Review GitHub PRs and GitLab MRs with structured analysis including blast radius, security scanning, test coverage delta, breaking change detection, and performance impact.

Performs security-focused differential review of code changes (PRs, commits, diffs), adapting analysis depth to codebase size and generating comprehensive markdown reports.

Runs a structured quality control audit on codebases, covering tests, imports, static analysis, type checking, smoke tests, UI verification, file consistency, and documentation, producing a PASS/WARN/FAIL report.

Analyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios using pygount, with guidance on using language servers for symbol navigation.

Builds a local knowledge graph of a codebase using tree-sitter and graph algorithms, then answers architecture questions by querying the graph instead of reading many files, saving tokens.

Enforces an algorithm-first discipline: state Big-O, data structure, and algorithm family before writing loops, queries, or recursion, catching O(n^2), N+1, and brute-force defaults.