Skip to content

Skill

Checking Implementation Against Official Documentation

Checks code, configuration, API usage, runtime behavior, or design material against official documentation, standards, or primary vendor guidance.

Back to Skills

When to use

Checks code, configuration, API usage, runtime behavior, or design material against official documentation, standards, or primary vendor guidance - establishing version applicability, reporting source-bound findings with citations, and planning file-specific remediation with a confidence score.

  • Use when

    Use when an implementation must be validated against authoritative guidance, especially for version-sensitive framework, library, runtime, API, or protocol behavior.

  • Limits

    Requires supplied authoritative sources or web access to them. Not for architecture classification or general code-quality review.

Skill package

checking-implementation-against-docs.zip

The ZIP contains the complete checking-implementation-against-docs folder: SKILL.md and 1 supporting file, at the paths the Skill uses.

  • checking-implementation-against-docs/SKILL.md
  • checking-implementation-against-docs/references/source-selection.md

Inputs required

Goal
The change, review question, or implementation decision to validate.
Implementation materials
Code, file tree, configuration, API usage, logs, or design and documentation excerpts.
Constraints
Language, framework, library, runtime, platform, API version, compatibility target, and non-functional limits.
Authoritative sources, or permission and capability to retrieve them
Official documentation, standards, or primary vendor references.

Access needed

Needs read access to the implementation under review and either supplied authoritative sources or web access to official documentation. Without either, the review stops with INSUFFICIENT_EVIDENCE. Read-only; does not modify files.