codex-skills

Maintains strict Python projects with Ruff, mypy, Pyright, pytest, editor, and package-script gates. Use when creating, auditing, or repairing strict lint, format, typecheck, test, compile, or VS Code tooling practices.

Validates and optionally performs dependency updates without weakening quality gates. Use when handling Dependabot/Renovate/npm-check-updates changes, lockfile review, update-tool runs, or code/config/type/lint/build/test fallout.

Maintains SchemaStore PRs. Use when working in SchemaStore/schemastore on JSON schemas, catalog entries, fileMatch patterns, tests, schema-validation.jsonc exceptions, CODEOWNERS-owned schemas, or PR readiness.

Generates copy-pasteable vscode-icons association objects. Use when mapping workspace filenames, extensions, generated files, dotfolders, test/config/framework folders, or other paths to supported VS Code Icons names.

Creates agent skill and instruction surfaces. Use when authoring SKILL.md folders, AGENTS.md/AGENTS.override.md, CLAUDE.md, Copilot or Cursor rules, or when asked to bootstrap, design, scaffold, or migrate reusable agent guidance.

Audits and improves agent skill and instruction surfaces. Use when reviewing SKILL.md, AGENTS.md/AGENTS.override.md, CLAUDE.md, Copilot or Cursor rules, or when asked to lint, score, modernize, deduplicate, secure, or repair agent guidance.

Validates release readiness and debugs CI failures. Use when inspecting GitHub Actions runs, failed checks, dependency-update validation, release gates, release-candidate prep, or readiness loops that must not publish without approval.

Maintains code-review quality across repos, files, configs, and low-confidence claims. Use when reviewing codebases/files, brittle implementations, consistency drift, comment triage, correctness, maintainability, security, release, or test risks.

Maintains repository docs, TSDoc, TypeDoc output, API comments, and Docusaurus sites. Use when fixing docs drift, TypeDoc diagnostics, TSDoc quality, broken examples/links, or polishing an existing Docusaurus portal.

Builds, audits, and maintains ESLint plugin repos. Use when scaffolding plugins, auditing best practices, syncing rule docs/tests/presets/generated surfaces, or discovering and implementing high-value net-new ESLint rules.

Maintains GitHub Actions workflows. Use when creating, reviewing, editing, or hardening .github/workflows YAML, workflow_call callers, CI/CD automation, action pinning, permissions, npm publishing, caching, matrices, actionlint, or review comments.

Validates and repairs lint, ESLint, and static-analysis diagnostics at the root cause. Use when running lint, resolving errors/warnings, removing unnecessary disable comments, or replacing suppressions with code, type, config, or test fixes.

Maintains Mermaid diagrams and config. Use when creating, editing, reviewing, theming, or debugging Mermaid flowcharts, sequence/ER/Gantt diagrams, dark themes, themeVariables, frontmatter config, renderer issues, or Markdown blocks.

Builds, audits, and maintains Prettier plugin and shared config repos. Use when scaffolding plugins, fixing parsers/printers/options, auditing doc-builder behavior, testing formatting output, or validating package/editor/CI integration.

Executes authorized release publishing. Use when the user explicitly asks Codex to commit/push, watch CI and SonarCloud/SonarQube gates, fix failed checks, choose semver, dispatch publish or release workflows, and verify artifacts.

Builds, audits, and maintains remark and remark-lint plugin repos. Use when scaffolding plugins, creating or repairing remark-lint rules, auditing unified/Markdown AST usage, syncing docs/tests/configs, or validating package/CLI behavior.

Builds, audits, and maintains Stylelint plugin repos. Use when scaffolding plugins, auditing best practices, discovering/implementing domain-specific rules, or syncing docs, tests, configs, and package validation.

Generates, repairs, and improves tests and coverage. Use when writing unit tests, fixing failures, improving meaningful coverage, testing error handling, adding Playwright E2E tests, or creating focused benchmarks.

Generates compact handoffs and continues active plans from workspace state. Use when resuming work, carrying a plan through implementation and validation, or summarizing work for a fresh session without rediscovery.