with one click
docs
// Update project documentation when features are added or changed. Use after modifying CLI commands, OPA rules, MCP tools, or the development workflow.
// Update project documentation when features are added or changed. Use after modifying CLI commands, OPA rules, MCP tools, or the development workflow.
Run code formatting and linting after writing or modifying Go code. Use this after making code changes to ensure quality standards are met.
Run snapshot regression tests after changes to OPA rules, scanners, analyzers, or formatters to detect output regressions.
Update the embedded build platform vulnerability database from the CVE Project's cvelistV5 repository.
| name | docs |
| description | Update project documentation when features are added or changed. Use after modifying CLI commands, OPA rules, MCP tools, or the development workflow. |
| paths | opa/rego/**, cmd/**, docs/**, README.md, MCP_INTEGRATION.md, CONTRIBUTING.md |
Review recent code changes and update all relevant documentation:
Rule documentation (docs/content/en/rules/<rule_id>.md):
---
title: "Rule Title"
slug: rule_id
url: /rules/rule_id/
rule: rule_id
severity: error|warning|note
---
## Description
## Remediation
## See Also
docs/content/en/rules/ for format guidanceREADME.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.