Results for “audit”

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Prüft Auditrechte-Klauseln in AGBs: ordnet Sachverhalt, Normen, Beweislast und Gegenargumente, liefert eine Fristen- und Risikoampel mit Sofortschritten und erstellt Redline-Entwürfe.

Audits design quality across accessibility, performance, theming, and responsiveness, producing a prioritized report with severity ratings and fix recommendations.

Audits image assets across a project to find missing, broken, or mismatched images, and generates prompts for missing assets.

Audits decisions and situations for operating psychological biases using Munger's 25 tendencies framework, producing a structured analysis with countermeasures.

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Generate full prospect audit as a sales tool before demos. Combines company research, CRO audit, and person intel into a presentable document with talking points and opportunity sizing.

Audit CI/CD pipelines (GitHub Actions) for cost, speed, and safety. Use when the Actions bill is high, Actions minutes, runner cost, slow CI, artifact/cache storage, or "CI/CD / workflow audit". Gate logic (bypass, ratchet gaming, required-but-not) → audit-gate-logic.

Donahoe Loop audit gate before execution. Trigger: 'audit plan', 'check plan', 'review plan', 'plan audit', 'plan check', 'before we build', 'before execution', 'validate the plan', 'is this plan solid', 'plan review'. Owns pre-execution audit intent -- fires before any foreign plan-checker.

Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness. Builds a translation coverage matrix, flags stale translations, validates hreflang and schema, and emits a prioritized report with runnable fix commands. Use when user says "locale audit", "blog locale-audit", "check translations", "multilingual audit", "translation check", "hreflang check", "Uebersetzungen pruefen".

Audit design token usage across a product for consistency and coverage, identifying hard-coded values and gaps.

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Audit screens against Nielsen's heuristics and mobile UX best practices, producing a prioritized issue list with remediation suggestions.

Audits screens against Nielsen's 10 heuristics and mobile UX best practices, producing a prioritized issue list with remediation suggestions.

Automated WCAG 2.2 accessibility audit using playwright-cli to crawl every page, inject axe-core via eval, test keyboard navigation, check color contrast, ARIA labels, and heading order. Use when "audit accessibility", "check a11y", "WCAG audit", "check keyboard nav", or "test screen reader".

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns.

Apply-now consolidation of accreted CI gates, ratchets, and hooks into one aggregator required check. Use after audit-gate-logic, or when "clean up our CI checks", "we have three lint jobs", "make one quality gate". Audit-only → audit-gate-logic. Pipeline cost → audit-cicd.

Measure Jetson DRAM and NvMap usage, capture before/after baselines, and verify memory reclamation with live audit data.

Audit screens against Nielsen's heuristics and mobile UX best practices using the StyleSeed Toss design language as the implementation context.

Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness, returning a structured report with exact patch locations.

Audits code quality against a shared contract, returning structured findings without modifying code. Supports gate, audit, diff, changed, and verify modes.

Audits type safety documentation against the live codebase and fixes errors, gaps, or stale information to keep docs authoritative.

Audits a repository for comment coverage and brings under-commented source files up to standard, one file at a time, with a resumable tracker.

Audit codebase for opportunities to reduce lines of code while preserving functionality, performance, and quality

Pressure-tests medical-device QMS work with six traceability-obsessed questions before internal audits, regulatory reviews, or product launches.

Pressure-tests an ISMS with six sample-driven questions to prepare for ISO 27001 internal, certification, or surveillance audits.

Audit MCP server configurations for security issues including secrets exposure, shell injection, unpinned dependencies, and unapproved servers.

Provides grep scan commands for auditing React codebases before upgrading to React 18.3.1 or React 19.

Runs systematic quality checks across accessibility, performance, theming, and responsive design, then generates a prioritized audit report with actionable recommendations without fixing issues.

Audita e diagnostica SEO técnico, on-page e qualidade de conteúdo, priorizando problemas por impacto e esforço.

Audits Vue 3 components for design-system consistency, legacy patterns, and missing states, producing a component log.

Regulatory compliance and audit agent. Maps business regulatory requirements (SOC2/PCI-DSS/HIPAA/ISO 27001), checks control implementations, designs audit trails, and implements Policy as Code. Use when compliance auditing is needed.

Deep technical SEO audit covering Core Web Vitals, crawlability, indexation, structured data, canonical/hreflang, redirect chains, and site architecture. Complements seo-auditor which focuses on on-page/off-page factors.

Read-only audit of unhappy-path UI states vibe-coding skips — empty, loading, error, offline, zero-results, permission, overflow — then plan fixes. Use when "check empty/error states", "audit loading states", or "what happens when this fails". Dead buttons → plan-stub-checker; backend timeouts → audit-resilience.

Read-only audit of a codemod or bulk mechanical transform for behavior-preservation — compiles/lints is not same-behavior. Use when "did this codemod break anything", "audit this bulk refactor", or before merging a mass find-replace. Diff quality → audit-code-review. SQL → plan-data-integrity.

Use the release-audit skill to run the pre-release validation sweep and print