Awesome Code Review Feedback
How to respond to code review feedback: verify before implementing, clarify unclear items, and push back with technical reasoning when needed. Use when receiving PR feedback or review comments, when reviewer or bot findings need addressing, or when the user says 'address the review', 'ответь на ревью', 'поправь по замечаниям'. Applies to any team or culture. Do not use for performing the review i…
Awesome Security Audit
Audits code for common vulnerabilities: injection, secrets, auth, dependency CVEs, CI/CD pipeline exposure, and cryptographic misuse — with confidence-gated, evidence-backed findings mapped to CWE/OWASP. Use when reviewing security, before a release, after adding auth/payments/sensitive-data handling, when hardening GitHub Actions or other CI workflows, or when the user says 'security review', 's…
Awesome Dependency Upgrade
Plans and executes dependency upgrades safely — batching by risk, changelog-driven major migrations, overrides for unfixed CVEs, verification between steps, one revertable commit per batch. Use when asked to 'upgrade dependencies', 'bump packages', 'fix the audit findings', 'update to the latest version', 'обнови зависимости', or to act on an awesome-dependency-audit report. Do not use for detect…
Awesome Api Design
Designs or reviews the shape of an HTTP API before code exists — resource modeling, versioning strategy, pagination, idempotency, filtering, and how the error contract plugs in. Use when asked to 'design the API', 'review my API design', 'how should we version / paginate', 'add an endpoint' at the design stage, or when awesome-design-doc needs the API contract detailed. Do not use for the error e…
Awesome Code Standards
Universal coding standards: naming, structure, immutability, error handling, type safety, plus backend layering and frontend architecture/motion patterns for consistent code. Use when starting a project or module, refactoring to team conventions, setting up lint/format rules, onboarding, or when the user says 'coding standards', 'naming conventions', 'code style', 'стандарты кода'. Discovers and…
Awesome Humanize En
Use when: the user asks you to check, rewrite, humanize, or de-slop English text that shows signs of AI generation (ChatGPT, Claude, Gemini, Grok, DeepSeek, GPT-5, Qwen, Llama, any LLM). Trigger for requests like: 'humanize this', 'make it sound human / natural', 'remove the AI voice', 'this reads like a chatbot', 'AI detector for English', 'check for AI', 'de-slop', 'reduce AI-isms', remove clic…
Awesome Logging Standards
Applies structured logging, levels, PII handling, and wide-event (canonical log line) patterns. Use when adding or reviewing logs, choosing log levels, designing request logging, after an incident where logs were insufficient or leaked data, or when the user says 'logging', 'log format', 'what should we log', 'логирование'. Do not use for designing the error contract or retry policy itself — use…
Awesome Pentest
Runs an authorization-gated penetration-test engagement against a target (repo, web app, API, network, cloud, or mobile client) following PTES, OWASP WSTG/MASTG/API Top 10, and NIST SP 800-115 — from scoping and rules of engagement through recon, attack-surface mapping, testing, exploitation-to-proof, and a findings report with CWE/CVSS and retest. Passive review of your own code needs no gate; a…
Awesome Document Style
Clean and line-edit Markdown documents for clear, specific, publication-ready prose. Use when asked to de-bloat, de-template, remove chatbot artifacts, fix vague wording, settle whether numbers are written as digits or spelled out, or make Markdown read like careful human editorial writing. Do not use to fabricate facts or bypass detectors.
Awesome Architecture Audit
Read-only whole-project deep audit — architecture and module boundaries, documentation-vs-code fidelity, design-principle adherence (YAGNI/KISS/SOLID), and extensibility (how easily someone builds from source and adds a new provider/plugin/adapter) — producing a prioritized report with a SHIP / FIX / BLOCK verdict. Framework- and language-agnostic. Use when the user asks to 'audit/analyze the arc…
Awesome Leak Audit
Audit a public-facing client (browser extension, mobile/desktop app, SPA, CLI, SDK, or any open-sourced client that talks to a private backend) so its public surface stays self-contained and doesn't help attackers. Use when asked to review a repo for leaked backend internals, secrets, or abuse-enabling disclosure; to check that comments/docs/tests don't reveal server-side mechanics (rate limits,…
Awesome Error Standards
Applies consistent error handling, logging, and user-facing messages: typed errors, operational-vs-programmer classification, API error envelopes, HTTP status mapping. Use when adding or refactoring error handling, designing an API error contract, reviewing failure paths, or when the user says 'error handling', 'consistent errors', 'обработка ошибок'. Do not use for log format, levels, or PII red…
Awesome Bug Fix
Debugs by building a runnable pass/fail reproduction, isolating the root cause, then fixing — no fixes without root cause first. Use when fixing bugs, investigating test/build failures, or when the user reports an error, crash, flaky behavior, or says 'debug this', 'why does X happen', 'не работает'. Use especially under time pressure or after several failed fix attempts. Do not use for feature w…
Awesome Test Writing
Designs and writes tests that catch real regressions — placement (unit/integration/E2E), factories and fixtures, behavior-first assertions, characterization tests for legacy code, property/fuzz tests for parsers. Use when asked to 'write tests', 'add test coverage', 'test this module', 'напиши тесты', when a bug fix needs its regression test, or when awesome-bug-fix, awesome-code-review, or aweso…
Awesome Style Mimic
Learns a website's writing style by deep-crawling it in a live browser and distills a reusable style guide (voice, tone rules, lexicon, rhythm, structure templates, verbatim golden samples), then rewrites any documents or page sources in that voice with a cross-document consistency pass. Use when the user says 'learn the style of <site>', 'изучи стиль сайта', 'create a style guide from my website…
Awesome Root Cause
Structured root-cause analysis for incidents, recurring failures, and process problems that have no failing test to run — 5-Whys, fishbone, PDCA, and a one-page A3 write-up. Use for a postmortem, incident retro, 'why does this keep happening', quality or process breakdown, or 'find the root cause' of a non-code issue. For an actual code bug with a reproducible failure, use awesome-bug-fix instead.
Awesome Design Doc
Produces a design document or ADR for a feature or architectural decision: requirements and scale numbers first, real alternatives with trade-offs, a recommendation grounded in the requirements, explicit non-goals and migration path. Use when asked to 'write a design doc', 'write an ADR', 'design this feature/system', 'which approach should we take', 'спроектируй', or when awesome-code-review req…
Awesome Accessibility Audit
Audits UI and markup for accessibility (WCAG 2.1/2.2, keyboard, screen readers) and suggests concrete fixes. Use when checking a11y, before shipping a page or component, reviewing forms/modals/interactive UI, or when the user says 'accessibility', 'a11y', 'WCAG', 'screen reader', 'keyboard navigation', 'доступность'. Covers semantic HTML, focus management, labels, contrast, dynamic content, and W…
Awesome Dependency Audit
Read-only audit of a project's third-party dependencies — lockfile discipline, hallucinated and typosquatted package names (slopsquatting), dependency confusion, install-script exposure, maintenance and provenance, license conflicts, and CVE reachability — producing evidence-backed findings and a SHIP / FIX / BLOCK verdict. Use when the user asks to 'audit dependencies', 'check the supply chain',…
Awesome Git History Reset
Erases a repository's entire git history and replaces it with a single fresh commit, then force-pushes — safely: access checks, a verified mirror backup, a secret scan, and an explicit confirmation gate before anything irreversible. Use when asked to 'wipe git history', 'squash all commits into one', 'reset history to a single Initial commit', 'start the history fresh', 'clean/erase the commit lo…
Awesome Landing Audit
Read-only, mechanical audit of a landing or marketing page's conversion structure — single primary CTA per view, form-field friction, ad-to-headline message match, trust/social-proof presence, above-the-fold value, and CLS-safe banners/interstitials — producing evidence-backed findings and a SHIP / FIX / BLOCK verdict per page. Use when the user asks to 'audit my landing page', 'why isn't this pa…
Awesome Grammar Check
Advisory copy-edit of prose — reports grammar, logic, and flow issues as suggestions without rewriting the text. Use when the user asks to 'check grammar', 'proofread', 'copy-edit', 'find errors in', or 'review the writing' of an article, email, doc, or post, and wants to keep control of the wording. Not for removing AI-generated voice/markers (use awesome-humanize-en) and not for rewriting or de…
Awesome Db Audit
Read-only audit of a database layer — schema design against a catalog of SQL anti-patterns (EAV, generic keys, imprecise types), query patterns (SELECT *, N+1, unindexable predicates), integrity and concurrency (constraints in the DB, transactions, locking), and migration/operations hygiene (forward-only, expand/contract, restore path, tenancy model) — producing evidence-backed findings and a SHI…
Awesome Performance Audit
Read-only audit of performance and reliability — event-loop discipline, streaming and backpressure, memory/CPU diagnostics, production shutdown/timeout/job habits, cross-service resilience topology (circuit breakers, retry budgets, queue bounds, dual-writes), and frontend delivery (Core Web Vitals, bundle size, hydration) — producing evidence-backed findings and a SHIP / FIX / BLOCK verdict. Use…
Awesome Translate Ru En
Translate Russian text of any kind into natural English while preserving every structural element, formatting marker, link, identifier, and the author's human voice. Use when translating Russian articles, docs, prose, fiction, marketing copy, technical content, transcripts, or any other Russian-language text to English; when mirroring a directory of Russian files into an English equivalent; or wh…
Awesome Seo Audit
Read-only SEO and AI-discoverability audit of a site or codebase — technical SEO, generated-page (programmatic SEO) safety, and agent/LLM readability — producing evidence-backed findings and a SHIP / FIX / BLOCK verdict. Use when the user asks to 'audit my SEO', 'check for thin content / cannibalization', 'will Google penalize these pages', 'am I blocking GPTBot/ClaudeBot', 'llms.txt', 'AI discov…
Awesome Code Review
Reviews diffs and PRs for correctness, security, and team standards, with confidence-scored findings in severity buckets (Critical / Suggestions / Nice to have). Use when reviewing a pull request, merge request, patch, or diff; before merging; after completing a feature; or when the user says 'review this PR', 'check this change', 'review my diff', 'сделай ревью'. Do not use for responding to rev…
Awesome Code Cleanup
Repo-wide audit and cleanup of AI-like code noise — comments to a strict best-practice bar (delete redundant/narrating, condense bloated, fix stale or misleading, keep only load-bearing knowledge), plus a read-only audit mode and an opt-in refactor mode for vague names, dead/duplicated/speculative code, and over-abstraction — all strictly behavior-preserving and verified. Use whenever the user as…