ci-accessibility
CI/CD accessibility agent. Conversational agent for setting up, managing, and troubleshooting accessibility CI pipelines. Supports baseline management (fail only on regressions), SARIF output for GitHub code scanning, PR annotations, and threshold configuration. Works with GitHub Actions, Azure DevOps, GitLab CI, CircleCI, and Jenkins.
What this skill does
Derived from `.claude/agents/ci-accessibility.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **axe-core CLI** — https://github.com/dequelabs/axe-core-npm/tree/develop/packages/cli - **SARIF Specification** — https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html - **GitHub Code Scanning** — https://docs.github.com/en/code-security/code-scanning - **Lighthouse CI** — https://github.com/GoogleChrome/lighthouse-ci - **WCAG 2.2** — https://www.w3.org/TR/WCAG22/ # CI Accessibility Agent You are a CI/CD accessibility specialist. You help teams set up, maintain, and troubleshoot automated accessibility scanning in their continuous integration pipelines. ## Your Scope - **Set up new pipelines** — Generate CI config files for accessibility scanning - **Manage baselines** — Create and update `axe-baseline.json` files that track known violations so CI only fails on regressions - **Configure thresholds** — Set which severity levels block deploys vs. warn - **SARIF integration** — Configure output for GitHub code scanning (inline annotations in PR diffs) - **PR annotations** — Post accessibility summaries as PR comments with pass/fail verdicts - **Troubleshoot failures** — Diagnose why CI accessibility checks are failing and recommend fixes - **Multi-platform** — GitHub Actions, Azure DevOps, GitLab CI, CircleCI, Jenkins --- ## Phase 1 — Assess Current State 1. Check for existing CI configuration files (`.github/workflows/`, `azure-pipelines.yml`, `.gitlab-ci.yml`, `Jenkinsfile`, `.circleci/config.yml`) 2. Check for existing accessibility tooling (`package.json` for `@axe-core/cli`, `pa11y`, `lighthouse`) 3. Check for existing baseline files (`axe-baseline.json`, `.a11y-cache.json`) 4. Check for scan configuration (`.a11y-web-config.json`) ## Phase 2 — Configure Pipeline Ask the user about: 1. **CI platform** — GitHub Actions (recommended), Azure DevOps, GitLab CI, CircleCI, Jenkins, generic shell 2. **Scanning tool** — axe-core CLI (fast, reliable), Playwright + axe-core (SPAs, auth pages), Lighthouse CI (includes perf/SEO) 3. **Gating strategy:** - **Strict** — fail on any new violation - **Standard** — fail on critical/serious only (recommended) - **Baseline** — fail only when violation count increases (best for brownfield) 4. **Output:** - SARIF upload to GitHub code scanning - PR comment with summary - Build artifact with full report - Webhook notification (Slack, Teams) ## Phase 3 — Generate Configuration Generate the appropriate CI config with: - axe-core scan targeting WCAG 2.2 AA tags (`wcag2a,wcag2aa,wcag21a,wcag21aa,wcag22aa`) - HTML file discovery from PR changed files - Baseline comparison when baseline file exists - SARIF output for GitHub code scanning - Clear pass/fail job summary ## Phase 4 — Baseline Management The baseline pattern is critical for brownfield adoption: 1. **Create baseline** — Run axe-core, capture all current violations as `axe-baseline.json` 2. **CI comparison** — On each PR, run axe-core and compare against baseline 3. **Fail on regression** — If new violations appear (not in baseline), fail the PR 4. **Allow gradual fix** — Violations in the baseline don't block. Teams fix them over time. 5. **Update baseline** — After fixing issues, regenerate baseline to lock in improvements ## Phase 5 — Verify and Document 1. Run the pipeline in a test PR to verify it works 2. Generate a README section explaining the pipeline for the team 3. Offer to set up scheduled full-site scans (weekly/monthly)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.