exeris-doc-impact-triage
Evaluates the documentation impact of code changes to determine required review levels.
Install
mkdir -p .claude/skills/exeris-doc-impact-triage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10748" && unzip -o skill.zip -d .claude/skills/exeris-doc-impact-triage && rm skill.zipInstalls to .claude/skills/exeris-doc-impact-triage
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Router/Planner docs skill for Exeris Kernel. Classifies expected documentation/ADR impact and required review level.Key capabilities
- →Classify documentation impact as minor or none
- →Identify when documentation review is required
- →Detect potential Architectural Decision Record (ADR) review needs
- →Assess changes in terminology, configuration, or defaults
- →Evaluate observable behavior changes
- →Determine if architectural intent has changed
How it works
The skill applies a set of triage rules to classify the impact of changes on documentation and Architectural Decision Records based on behavior, contract, and architectural intent.
Inputs & outputs
When to use exeris-doc-impact-triage
- →Checking doc impact
- →Triage ADR review
- →Assessing behavioral changes
About this skill
Exeris Doc Impact Triage
Purpose
Quickly detect documentation and ADR drift risk in triage.
Output Contract
Return exactly one status:
NO_DOC_IMPACTMINOR_DOC_IMPACTDOCS_REVIEW_REQUIREDADR_REVIEW_POSSIBLE
And return:
whysuggested_doc_action
Triage Rules
- No behavior/contract/boundary change -> likely
NO_DOC_IMPACT. - Terminology/config/default changes -> often
MINOR_DOC_IMPACT. - Observable behavior change or subsystem contract drift ->
DOCS_REVIEW_REQUIRED. - Architectural intent/boundary meaning changes ->
ADR_REVIEW_POSSIBLE.
Completion Criteria
Classification is complete only if status and action are both explicit.
When not to use it
- →When the task is not related to documentation or ADR impact assessment
- →When a detailed code review is needed instead of impact classification
Limitations
- →Returns exactly one status classification
- →Requires explicit status and action for completion
- →Focuses on documentation and ADR drift risk
How it compares
This skill provides a structured classification of documentation and ADR impact, which differs from a manual, unguided assessment of changes.
Compared to similar skills
exeris-doc-impact-triage side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| exeris-doc-impact-triage (this skill) | 0 | 4mo | No flags | Beginner |
| architecture-decision-records | 54 | 5mo | Review | Beginner |
| wiki-architect | 11 | 3mo | No flags | Advanced |
| smart-docs | 4 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
architecture-decision-records
wshobson
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
smart-docs
sopaco
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.
codebase-documenter
mhattingpete
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
c4-architecture-c4-architecture
sickn33
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
dagger-design-proposals
dagger
Write design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.