docs

SkillDocs & knowledge

Update project documentation when features are added or changed. Use after modifying CLI commands, OPA rules, MCP tools, or the development workflow.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the docs skill

What this skill tells your AI

The instructions your AI receives, as published by boostsecurityio/poutine in .claude/skills/docs/SKILL.md and read by ahel’s review.

Review recent code changes and update all relevant documentation:

Rule documentation (docs/content/en/rules/<rule_id>.md):
- If a new rule was added, create a new markdown file following the existing format:
```
---
title: "Rule Title"
slug: rule_id
url: /rules/rule_id/
rule: rule_id
severity: error|warning|note
---
## Description
## Remediation
## See Also
```
- If an existing rule was modified, update its description, remediation, or examples
- Reference existing rule docs in docs/content/en/rules/ for format guidance
README.md — Update if CLI commands, flags, or usage patterns changed
MCP_INTEGRATION.md — Update if MCP tools were added, removed, or changed
CONTRIBUTING.md — Update if development workflow, testing, or build process changed
Structured finding metadata (docs/content/en/structured-finding-metadata.md) — Update if finding JSON fields changed

Read the changed files first to understand what needs documenting, then make the updates.

Advanced