Results for “pr-review”

Use `analysis-agent` for release decisions, `task-agent` for delivery artifacts, or `review-agent` for readiness on deployment, migration, rollback, or production risk. Skip local work with no release decision.

Creates data-driven infographics and charts as accessible SVG. Use when visualizing data, choosing a chart type, generating an SVG chart or infographic, or reviewing a visualization for clarity and accuracy.

Use when the team needs authentication, identity providers, custom claims, session strategy, or permission design for a Firebase-backed app. Trigger on requests to design or review Firebase Auth architecture.

Write, review, and migrate code using NVIDIA DALI's imperative dynamic-mode API for efficient data loading and preprocessing.

Build, review, or troubleshoot Lightning Web Components that run inside Salesforce Flow screens, covering @api properties, FlowAttributeChangeEvent, validate(), and navigation events.

Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, styling React views, or enforcing design consistency.

Stops AI from generating boring, generic UI. Use when building new interfaces, reviewing generated UI, or fixing the flat / generic look that AI tools default to. Anti-slop design principles for premium frontends.

Use before delivering any documentation to validate quality, accuracy, and completeness. This skill provides a checklist for reviewing all documentation deliverables to ensure they meet minimum quality standards before distribution.

Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, styling React views, or enforcing design consistency.

Use this when background workers or job processors need design or review. Trigger on requests about asynchronous processing, job payloads, retries, scheduling, worker ownership, or long-running tasks outside the request path.

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

Selects and reviews Queueable, Batch, Future, and Schedulable Apex for callouts, large data processing, retries, and background work, with decision guidance and validation checklists.

Creates or edits a GitHub pull request in draft state from a reviewed draft file, with strict safeguards against merging, pushing, or modifying tracked files.

Use when creating, maintaining, or reviewing records of actions, decisions, changes, and events for compliance, accountability, and investigation purposes. This skill provides procedures for managing audit trails across all agent activities.

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

Use this skill when the user asks about DataQ — FMCSA's data review system at dataqs.fmcsa.dot.gov — for disputing inspection violations, crash records, or other entries that appear in a carrier's CSA / SMS score. Covers Request for Data Review (RDR) process, success rates, common dispute grounds, what evidence to attach, timeline expectations, and how successful disputes reduce BSI (BASIC Severity Indicator) scores. Cite 49 CFR 392.7 and the FMCSA DataQs User Guide.

Use when writing or reviewing tests, or when asked how to write a good single test. Encodes the per-test rules behind the "test the contract / responsibility, not the implementation" principle — name and structure one behavior per `it`, drive through the public surface, stub only true external boundaries, control time and config via documented knobs, and keep tests clear, isolated, and refactor-resilient. The same rules drive both authoring (write mode) and auditing existing tests (review mode).

Audits test files for anti-patterns and quality issues, producing a severity-ranked report across multiple languages and frameworks.

Visually inspect websites to identify and fix design issues including layout, responsive, accessibility, and visual consistency problems at the source code level.

Manage software complexity through deep modules, information hiding, and strategic programming, with a scoring framework for evaluating design quality.

Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance for code, infrastructure, and cloud environments.

Interrogates a plan against real third-party documentation, extracting hard constraints and asking doc-cited questions before producing a constraints appendix.

Generates and maintains project documentation: Google-style docstrings, README, architecture docs, and ADRs, with a mandatory post-task review gate to keep docs current.

Audits a wiki for contradictions, stale content, orphan pages, duplicates, missing sections, broken wikilinks, and AI-tell contamination, producing a lint report for human review.

Generates, reviews, fixes, and migrates Playwright end-to-end tests, with templates, agents, and integrations for TestRail and BrowserStack.

Tailwind CSS v4 — utility-first styling, responsive design, dark mode, and component extraction. Use when building or reviewing Tailwind-based UIs, setting up Tailwind v4, or designing responsive or dark-mode styling.

Infrastructure-as-code with Terraform/OpenTofu — resources, state, modules, plan/apply. Use when writing `.tf` files, managing cloud infrastructure with Terraform or OpenTofu, handling state and backends, or reviewing IaC code.

Audit datasets for structure, missingness, labeling, suspicious values, duplicate identifiers, and documentation readiness. Use when a researcher asks for data QA, codebook review, sanity checks, or pre-analysis cleanup guidance.

Grades individual test methods and produces a compact markdown table with a letter grade, score band, and one-line note for each test.

Designs and reviews schedule-triggered flows for recurring automation, covering bounded record selection, idempotent processing, and escalation to Apex when volume is too high.

Write, review, debug, or interpret Python statistical models using statsmodels, including formulas, regression, GLM, time series, robust covariance, diagnostics, prediction intervals, and inference.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Designs or reviews Agentforce agent actions, covering Flow, Apex invocable, and prompt-template actions, including naming, input/output contracts, confirmation, and error behavior.

Drafts GitHub pull request titles, bodies, issue-closing footers, and maintainer ping comments, tailored to repo-specific commitlint or semantic PR conventions.

Drafts an audit-ready Export Compliance Program manual covering EAR, ITAR, and OFAC requirements. Use when creating or updating an export compliance policy, international trade compliance program, or preparing enforcement defense documentation for regulatory review.