Skip to main content

Coding-Agent Skills

Skills are plain Markdown playbooks that live in .claude/skills/. Any team member can invoke them with a /skill-name slash command in Claude Code, and the agent follows the same steps every time β€” consistent, reviewable, no ad-hoc prompting required.


Available skills​

πŸ“ /release-docs​

Generate a combined release blog post for a new version.

Use when: cutting a release or when someone asks "what changed in 0.4.x"

Produces: docs/releases/YYYY-MM-DD-release-X-Y-0.md, one post per minor series, slugged release-X.Y.0, containing the narrative and upgrade guide, picked up by the Docusaurus releases plugin. Each post covers the cumulative diff since the previous minor's .0. An X.Y.0 tag starts a new post; patch releases fold into the existing post rather than getting one of their own.

Inputs: to-version, from-version (auto-detected from git tags if omitted), optional values.yaml for personal impact analysis.

β†’ View skill source


πŸ”„ /update-docs​

Audit and sync all documentation surfaces after a release or feature addition.

Use when: after cutting a release, adding a new agent, or updating platform features.

Checks:

#SurfaceStale when…
1Release notesAn X.Y.0 tag has no docs/releases/ series post, or a series post omits later patches
2Homepage version stringHelm --version in index.tsx is behind latest tag
3Published versionsA released tag is missing from docs/published-versions.json
4Features page tilesNew feature docs without a tile in features.tsx
5MCP docsPackaged MCP integration without current docs
6SidebarDoc directory not in sidebars.ts
7Navbar labelVersion label behind latest tag

β†’ View skill source


πŸ§ͺ /integration-testing​

Run the full end-to-end integration test suite against a running Docker Compose stack.

Use when: validating a feature branch before raising a PR, or after a major refactor.

β†’ View skill source


🚦 /quality-gates​

Run all pre-commit quality gates β€” lint, Python tests, UI tests β€” in one command.

Use when: before raising a PR or after resolving merge conflicts.

# Run all gates
./skills/quality-gates/run_all.sh

# Auto-fix lint first, then validate
./skills/quality-gates/run_all.sh --fix

β†’ View skill source


Adding a new skill​

See Create a Skill for the full guide. The short version:

  1. Create .claude/skills/<your-skill-name>/SKILL.md
  2. Add an entry to .claude/skills/README.md
  3. Add a row to the table above

The skill is immediately available as /your-skill-name to anyone using Claude Code in this repo.