grishaangelovgh/gemini-cli-agent-skills

Overview

This skill is an expert code reviewer focused on code quality, security, performance, and maintainability across multiple languages and stacks. It applies proprietary checklists and a mandatory review template stored in the skill's assets and references for consistent, repeatable analyses. Reviews produce prioritized, actionable feedback with examples and suggested fixes. The output emphasizes clarity, correctness, and practical remediation steps.

How this skill works

I inspect code for correctness, edge cases, and logical errors, then evaluate readability, test coverage, and adherence to idiomatic patterns. I run security and performance heuristics using the included security checklist and language-specific guides in references. Every comprehensive review follows the mandatory REVIEW_TEMPLATE in assets and returns a summary followed by prioritized findings, examples, and remediation suggestions. I also pose clarifying questions when intent or requirements are unclear.

When to use it

• When submitting a pull request that needs a formal review across correctness, security, and performance.
• Before merging high-risk changes, refactors, or new feature implementations.
• When you want language-idiomatic feedback using the skill's specialized guides (e.g., Python, JavaScript, Go).
• To verify tests cover edge cases and error paths and to get suggestions for improving test quality.
• To identify hardcoded secrets, insecure handling of inputs, or other security vulnerabilities.

Best practices

• Provide a focused diff or PR link and describe the intended behavior and constraints up front.
• Include failing tests or minimal repro steps for bugs — this speeds diagnosis and validation of fixes.
• Allow the review to run against the whole module or package when refactors may affect cross-file behavior.
• Respond to follow-up clarification questions to narrow assumptions before major rewrites.
• Treat findings as prioritized: fix critical security and correctness issues first, then address performance and style improvements.

Example use cases

• Full PR review for a backend API change that may affect authentication and database access.
• Security audit of code handling user input, file uploads, or external integrations.
• Performance review for hot paths, identifying algorithmic bottlenecks and expensive I/O inside loops.
• Pre-merge review of a large refactor to ensure maintainability and consistent style across modules.
• Test-suite evaluation to increase coverage for edge cases and to harden integration tests.