skyosev/agent-skills
Skill Claude CodeCodex
Use when reviewing Go, Python, or TypeScript code for over-engineering, reducing complexity after prototyping, enforcing reuse over addition, simplifying before a refactor, or auditing a codebase after a library or framework migration. Covers duplication, reinvented primitives, avoidable abstractions, dead logic…
skyosev/agent-skills
Skill Claude CodeCodex
Use when reviewing Go, Python, or TypeScript code for classic code smells, preparing a refactor, auditing code after rapid feature development, or hunting for misplaced responsibilities and undermodeled domain concepts. Covers feature envy, data clumps, shotgun surgery, temporal coupling, comments as deodorant…
skyosev/agent-skills
Skill Claude CodeCodex
Review a GitHub pull request — fetches context, builds an intent model, runs 3 parallel review agents (Correctness, Conventions, Efficiency & Safety), validates findings against actual code, and publishes one structured review. Triggers on "review this PR", "review PR #123", "review github.com/owner/repo/pull/N"…
skyosev/agent-skills
Skill Claude CodeCodex
Act as a senior Go engineer performing a critical design and testing review. Evaluates architecture, patterns, idiomaticity, over-engineering, testing strategy, and proposes concrete improvements — all grounded in the codebase. Use when: reviewing a Go codebase for design soundness, testing robustness, or overall code…
skyosev/agent-skills
Skill Claude CodeCodex
Grilling session that challenges your requirements against the existing codebase. Reports omit empty sections — no placeholder headings, empty tables, or negative statements like "no issues found".
skyosev/agent-skills
Skill Claude CodeCodex
Clarify the user’s intent for vague, incomplete, or ambiguous clauses, statements, and requirements before modifying the code. Reports omit empty sections — no placeholder headings, empty tables, or negative statements like "no issues found".
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go packages for boundary violations — leaked internals via exports, coupling through shared types, import cycles, missing internal/ packages, over-exported APIs, and dependency direction violations. Use when: reviewing package structure, shrinking public API surface, enforcing encapsulation, preparing packages…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for missing documentation where the "why" is not obvious — obscure calculations, non-trivial business rules, surprising behavior, implicit constraints, workarounds, and missing godoc on exported symbols. Finds where a comment would save the next reader significant time. Use when: reviewing Go code for…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for weak invariants — unchecked errors, nil pointer risks, ignored context cancellation, unsafe type assertions, zero-value traps, panic/recover misuse, and missing validation at construction boundaries. Use when: tightening domain models, reducing panic risks, increasing error handling discipline, or…
skyosev/agent-skills
Skill Claude CodeCodex
Run all 10 Go code quality hunters in parallel as subagents and write each report to a timestamped reports folder. Covers boundary, doc, invariant, security, simplicity, slop, smell, solid, test, and type hunters. Use when: running a full Go codebase audit, scanning all quality dimensions at once, preparing for a code…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for security vulnerabilities — hardcoded secrets, injection risks (SQL, command, template, path), missing input validation at trust boundaries, insecure defaults, auth gaps, sensitive data exposure, unsafe package usage, and weak crypto. Use when: reviewing Go code before deployment, auditing trust…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for unnecessary structural complexity — duplication, reinvented primitives, avoidable abstractions, dead logic paths, over-parameterized APIs, deep nesting, interface pollution, channel misuse, mixed concerns, and coexisting abstraction generations left behind by unfinished migrations. Recommends the…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for AI-generated noise — redundant comments, verbose documentation, style drift from project conventions and gofmt, trivially dead code, and unnecessary error wrapping. Surface-level hygiene pass; defaults to branch diff but supports any scope. Use when: reviewing AI-assisted Go code before merge…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for classic code smells — feature envy, data clumps, shotgun surgery, primitive obsession, temporal coupling, comments as deodorant, temporary fields, init() abuse, package-level mutable state, and stuttering names. Use when: reviewing Go code for structural design problems, preparing for a refactor…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go code for design principle violations — god packages, rigid extension points, broken interface contracts, fat interfaces, and concrete dependency chains. Adapted from SOLID for Go's composition-over-inheritance model. Use when: reviewing package structure, preparing for extension with new variants, reducing…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go test code for quality gaps — missing coverage on critical paths, brittle tests coupled to implementation, over-mocking, assertion-free tests, missing edge cases, table-driven test misuse, and race condition blindness. Focuses on test effectiveness. Use when: reviewing Go test suites for reliability, reducing…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Go type definitions for design debt — duplicated struct shapes, misused generics, under-constrained type parameters, embedding antipatterns, poor enum patterns, and disorganized type architecture. Type structure and maintainability. Use when: reviewing type definitions for maintainability, reducing type…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python packages and modules for black-box boundary violations — leaked internals via exports, coupling through shared types, Law of Demeter chains, missing abstraction layers around externals, and over-exported APIs. Use when: reviewing package structure, shrinking public API surface, enforcing encapsulation…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python code for missing or misleading inline documentation where the "why" is not obvious — obscure calculations, non-trivial business rules, surprising behavior, implicit constraints, workarounds, and stale comments that contradict the current code. Finds where a comment would save the next reader significant…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python code for error handling design quality — missing exception hierarchies, lost exception chains, return-None antipatterns, over-broad try/except, silent suppression, poor exception context, framework handler gaps, and missing error boundaries. Use when: reviewing error handling strategy, tightening…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python code for weak invariants — unnecessary casts, loose optionality, defensive None-checks masking missing guarantees, leaky tagged unions, error suppression, and runtime checks that the type system or construction boundaries should enforce. Use when: tightening post-construction guarantees, reducing type…
skyosev/agent-skills
Skill Claude CodeCodex
Run all 12 Python code quality hunters in parallel as subagents and write each report to a timestamped reports folder. Covers boundary, doc, error, invariant, perf, security, simplicity, slop, smell, solid, test, and type hunters. Use when: running a full Python codebase audit, scanning all quality dimensions at once…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python code for performance antipatterns and resource management issues — blocking I/O in async contexts, sequential awaits, N+1 queries, unclosed resources, unbounded caches, eager materialization, missing connection pooling, and expensive operations in hot paths. Use when: reviewing async correctness, auditing…
skyosev/agent-skills
Skill Claude CodeCodex
Audit Python code for security vulnerabilities — hardcoded secrets, injection risks, missing input validation at trust boundaries, insecure defaults, auth gaps, sensitive data exposure, and unsafe patterns like eval, pickle, or shell injection. Use when: reviewing Python code before deployment, auditing trust…