All authors

Claude Skills by gvago
github.com/gvago22 skills0 installs0 views
- Accessibility ReviewUse when a PR diff touches UI code - HTML, JSX/TSX, Vue/Svelte/Angular templates, CSS, or mobile view code. Enforces the WCAG 2.2 AA success criteria that are checkable in a diff - text alternatives, semantic structure, programmatic labels, name/role/value on custom widgets, keyboard access, focus visibility and management, color-only information, link purpose, autoplay media, pointer alternatives and target size, predictable interactions, page language and title, label-in-name, status messag...Votes: 0GitHub stars: 2
- Apex ReviewUse when a PR diff adds or modifies Salesforce Apex (.cls / .trigger) or SOQL/SOSL, flags governor-limit killers (SOQL/DML inside loops), missing CRUD/FLS & sharing enforcement, SOQL injection, hardcoded IDs, trigger anti-patterns, and swallowed exceptions in the CHANGED code only. Skip for non-Apex diffs.Votes: 0GitHub stars: 2
- Appsec Compliance ReviewUse when a PR diff touches application code, or any committed configuration that can carry credentials, governed by an organization's written security policy. Enforces five AppSec rules on the CHANGED code only - authentication/authorization on sensitive endpoints, injection, SSRF, debug/test code reachable in production, and hardcoded secrets - reporting per-rule per-file coverage so an unevaluated rule is never a silent skip. Skip only for docs-only diffs.Votes: 0GitHub stars: 2
- Behavioral Contract ReviewReview changes to lifecycle/state transitions, destructive operations, repository helper/API usage, tests, and behavior described in prose documentation. Detect changed-code violations of lifecycle invariants, established semantic contracts, effective test coverage, and code/document consistency. Include docs-only behavior claims; skip formatting-only changes without semantic impact.Votes: 0GitHub stars: 2
- Clang FormatUse when a PR changes C or C++ formatting governed by clang-format or .clang-format, including indentation, braces, spacing, alignment, include ordering, line breaking, macro-sensitive layout, or formatting-only review.Votes: 0GitHub stars: 2
- Commit Message ReviewUse when reviewing any Gerrit change or PR that has a commit message, verifies the message against the diff: claim/code mismatches (message says fix, diff adds a feature), unmentioned user-visible behavior changes, vague messages on non-trivial diffs, implausible ticket or issue ids. Fires on every review where a commit message is visible.Votes: 0GitHub stars: 2
- Coordinated Config Implementation ReviewUse when a config or client change depends on an endpoint, configuration consumer, or interface in another repository. Inspect linked or same-ticket companion PRs before reporting missing implementation; skip changes with no cross-repository dependency.Votes: 0GitHub stars: 2
- Design Doc ConformanceUse when reviewing any change in a repo that contains design documents (docs/design*.md, docs/adr/*.md, or a dedicated context repo), verifies the implementation against those committed docs: contradictions of explicit design statements, new public interfaces absent from the design, cited to the doc line. Fires whenever design docs exist in the repo under review.Votes: 0GitHub stars: 2
- Guideline DistillerUse when asked to convert, distill, or restructure a prose coding guideline, style guide, review checklist, or team-conventions markdown file into atomic enforceable review rules for the Qodo portal, or when prose guidelines are catching too few violations in review.Votes: 0GitHub stars: 2
- Kernel Change IntentUse when reviewing a Linux kernel PR diff, verifies commit goal and implementation claims (Sashiko stages 1-2): design soundness, UAPI/ABI breakage, and commit-message-vs-code mismatches in the CHANGED code only. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Driver HardwareUse when a Linux kernel PR diff touches driver hardware interaction, register access, DMA mapping, memory barriers, IRQ handlers, device power/state machines (Sashiko stage 7). Skip for purely generic software logic (VFS, core networking). Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Execution FlowUse when a Linux kernel PR diff changes C/Rust control flow, traces execution statically (Sashiko stage 3): broken error paths, NULL derefs, uninitialized or stale values, off-by-one loop logic, preprocessor/linkage hazards in the CHANGED code only. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Locking ConcurrencyUse when a Linux kernel PR diff touches locks, atomics, RCU, IRQs, or deferred work, concurrency audit (Sashiko stage 5): races, deadlocks, lock-context violations, missing barriers, RCU misuse. Every finding must name the two racing contexts. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Resource LifecycleUse when a Linux kernel PR diff allocates, frees, or hands off objects, tracks lifetimes (Sashiko stage 4): memory leaks on error paths, use-after-free, refcount imbalance, and asymmetric async teardown (missing cancel_work_sync and friends) in the CHANGED code only. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Review DisciplineALWAYS apply last when any linux-kernel-review suite lens produced candidate findings on a Linux kernel PR diff, the false-positive gate and severity calibration (Sashiko stages 9-10): prove-it-or-drop-it verification, conflict resolution, kernel severity mapped to the Qodo action contract. The noise killer for the suite.Votes: 0GitHub stars: 2
- Kernel Security AuditUse when a Linux kernel PR diff handles untrusted input (copy_from_user, get_user, ioctl args, netlink attrs, network or firmware data), security lens (Sashiko stage 6): OOB access, integer overflow, TOCTOU, info leaks to userspace, privilege escalation in the CHANGED code only. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Kernel Subsystem GuidesUse when a Linux kernel PR diff matches a known subsystem (mm, block, net, btrfs, io_uring, KVM, DRM, USB, scheduler, and 60+ more), router into per-subsystem invariant guides from Chris Mason's masoncl/review-prompts knowledge base; load every guide whose trigger row matches before analysis. Part of the linux-kernel-review suite.Votes: 0GitHub stars: 2
- Linux Kernel ReviewUse when a PR diff modifies Linux kernel code (C or Rust in a kernel tree: drivers/, fs/, mm/, net/, kernel/, block/, include/linux/, arch/), orchestrator for the kernel review suite: routes the diff through the kernel-* lenses, enforces the shared low-noise contract (prove it against the code, diff-scope only, few high-value findings). Skip for non-kernel diffs.Votes: 0GitHub stars: 2
- Qodo Calibrate RulesCalibrate the severity of every active Qodo rule across the workspace as one reviewable, reversible batch — export the active rules, propose a severity per rule from a fixed rubric, let the workspace admin approve or override each row, apply only what was approved, re-read the workspace to confirm it took, and revert the whole run from its receipt if asked — using the qodo CLI's managed rules tools. Use on "calibrate our rule severities", "recalibrate our rules", "recalibrate our review stand...Votes: 0GitHub stars: 2
- Terraform ReviewUse when a PR diff adds or modifies Terraform/OpenTofu (.tf / .tofu / .tftest.hcl), flags identity churn (missing `moved` blocks, `count` index churn), secrets that land in state, unsafe destroy/state ops, version-floor violations, and backend/state antipatterns in the CHANGED HCL only. Skip for non-IaC diffs.Votes: 0GitHub stars: 2
- Test Scenario PatternsUse when a PR adds or changes test scenarios (test functions, parametrized cases, test classes) in tests/. Classifies EVERY added or modified test scenario against the approved test-pattern catalog (TP-01..TP-06) and reports the match, including scenarios that are compliant.Votes: 0GitHub stars: 2
- Toml Portal Migration AuditUse when a repo still has a .pr_agent.toml and Qodo settings are managed in the portal, or when a portal setting change has no effect. Audits every toml key against the portal-managed key map and proposes the exact minimal removal diff so the portal becomes the single source of truth. Run it before touching any Qodo config.Votes: 0GitHub stars: 2