「audit」の検索結果

Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.

日本語の概要は準備中です。原文の説明を表示しています。

Read-only audit of a GitHub repository's security posture. Gathers ref protection (rulesets AND classic branch protection), Actions token permissions, code and supply-chain features (Dependabot, secret scanning, push protection, CodeQL), and repo hygiene toggles via `gh api`, then classifies findings against essential / recommended / advanced tiers into a PASS/GAP report. Makes NO changes. Use when reviewing a repo before open-sourcing or a release, auditing a public user-owned repo whose CI auto-commits to the default branch, verifying a hardening change actually took effect, or producing a baseline security posture report for a repository.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and repair Claude Code discovery symlinks for skills, agents, and teams. Compares registries against .claude/ directories at project and global levels, detects missing, broken, and extraneous symlinks, distinguishes almanac content from external projects, and optionally repairs gaps. Use after adding new skills or agents, after a repository rename or move, when slash commands stop working, or as a periodic health check.

日本語の概要は準備中です。原文の説明を表示しています。

Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.

日本語の概要は準備中です。原文の説明を表示しています。

Use when directing, building, or auditing React/Next.js Tailwind UI: visual direction, responsive/dark-mode retrofits, UX audits. Not for typography or motion: use typography-audit or ui-animation.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

日本語の概要は準備中です。原文の説明を表示しています。

Launches 5 parallel AI agents to produce a comprehensive restaurant audit with composite Restaurant Health Score (0-100), grade, and prioritized action plan

日本語の概要は準備中です。原文の説明を表示しています。

Audit a NowStack Mobile iOS app against the App Store Review Guidelines before submission - account deletion, IAP/Restore + no Stripe on iOS, Sign in with Apple parity, permission strings, App Privacy, AI disclosure, export compliance. Use for "ns ios audit" or "will my app pass App Store review".

日本語の概要は準備中です。原文の説明を表示しています。

Audit web pages and components against RAWeb 1.1 (Luxembourg Web Accessibility Framework). Use when reviewing existing code for accessibility compliance, generating audit reports, checking conformance levels, or preparing for Luxembourg accessibility certification. Covers all 17 themes with systematic test procedures. Default target: Level AA.

日本語の概要は準備中です。原文の説明を表示しています。

Audit mobile applications (iOS and Android) against RAAM 1.1 (Luxembourg Mobile Accessibility Assessment Framework). Use when reviewing existing mobile app code for accessibility compliance, generating audit reports, checking conformance levels, or preparing for Luxembourg accessibility certification. Covers all 15 themes with platform-specific test procedures. Default target: Level AA.

日本語の概要は準備中です。原文の説明を表示しています。

Audit AI systems for bias and fairness. TRIGGERS - Use when user needs help with ai-bias-audit related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Audit AI systems for bias with testing frameworks and mitigation strategies. TRIGGERS - Use when user needs help with ai-bias-auditor related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing processes for AI automation. TRIGGERS - Use when user needs help with ai-automation-audit related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Build audit trails for AI decision-making. TRIGGERS - Use when user needs help with ai-audit-trail related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing business processes to identify AI automation opportunities. TRIGGERS - Use when user wants to find AI opportunities, audit processes for automation, or assess AI readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Audit UX accessibility with WCAG. TRIGGERS - Use when user needs help with accessibility-audit-ux related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Audit workplace accessibility for compliance. TRIGGERS - Use when user needs help with accessibility-audit related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Audit an existing Quarkus + LangChain4j project against this stack's agentic conventions — a read-only conformance or gap-analysis review. Use when the user asks to audit, review, check, assess, or validate a Quarkus project against the LangChain4j agentic conventions, or wants to know whether an existing project conforms to (or is ready to adopt) this stack. User-invoked only.

日本語の概要は準備中です。原文の説明を表示しています。

REQUIRED skill for any security-related request. Use this skill whenever the user wants to find anything dangerous, sensitive, or risky in their code, files, or repository. This includes but is not limited to: scanning for secrets/keys/tokens/credentials, checking dependencies for vulnerabilities, auditing destructive commands for missing safeguards, reviewing files for PII or internal data before open-sourcing, checking .env files or git history for leaked credentials, or any request where the concern is "is this safe/secure/exposed?" This skill provides a structured audit methodology and checklist you MUST follow — do not attempt security reviews without it. Skip this skill ONLY for pure feature work, refactoring, bug fixes, or non-security code review.

日本語の概要は準備中です。原文の説明を表示しています。

Use when mapping audit targets to appropriate config or domain agents. Analyzes file types, patterns, and content to determine which agents should audit each file/target. Returns agents[] needed for audit workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.

日本語の概要は準備中です。原文の説明を表示しています。

Forensic scan for npm/PyPI supply-chain compromise (Shai-Hulud/TeamPCP campaigns) — checks persistence, hook injection, compromised packages, IOC strings, C2, dead-man switches. Use when auditing a machine or repo for malicious dependencies. Trigger on "supply chain audit", "check for compromised packages", "Shai-Hulud", "scan for malicious deps".

日本語の概要は準備中です。原文の説明を表示しています。

Holistic project audit across endpoints, versions, docs, security, quality, CI, and library dimensions. Use when checking overall project health or running a periodic cross-cutting audit. Trigger on "project health", "audit the project", "health check", "is this project in good shape".

日本語の概要は準備中です。原文の説明を表示しています。

Audit Dockerfiles and Compose files against the 10 common Docker mistakes — image security, build efficiency, runtime safety. Use when reviewing or hardening Docker configs. Trigger on "audit my Dockerfile", "check this Compose file", "Docker best practices", "is my container secure".

日本語の概要は準備中です。原文の説明を表示しています。