code-verify

Validates source-code comments against actual code across Python, Go, Helm, Dockerfiles, shell, and GitHub Actions.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill code-verify-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-verify
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/nova/.claude/skills/code-verify
Command: npx skills add https://github.com/witwave-ai/witwave --skill code-verify-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code comments drift out of sync with the code they describe as refactors rename parameters, change signatures, and reorganize APIs. This Skill detects those contradictions without auto-fixing them, since every mismatch is a judgment call between updating the comment or fixing the code. ## Core Features & Use Cases - Multi-language comment verification: Checks Python docstrings against function signatures, Go godoc against exported APIs, Helm values.yaml comments against template usage, Dockerfile comments against instruction layers, shell-script header comments against function bodies, and GitHub Actions workflow comments against step definitions. - Read-only findings log: Appends every mismatch to a dated memory file with status markers ([pending], [flagged], [fixed]) so a human reviewer or backlog counter can triage later. - False-positive guards: Skips missing annotations, stylistic deviations, generated/vendored code, and known-external value patterns to avoid noise. - Use Case: After a refactor that renamed function parameters across a Python and Go codebase, run this Skill to list every docstring and godoc comment that still references the old names, then let a human decide whether to update the docs or revert the code. ## Quick Start Ask the agent to verify code comments against reality across the repository and log any mismatches it finds.

Frequently Asked Questions about code-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if Python docstrings match function signatures?▼

Parse each Python file with ast.parse, extract parameter names, type annotations, and return types from FunctionDef nodes, then compare them against docstring sections like Args:, Returns:, or :param: directives. Flag claims that contradict the signature, but skip cases where the signature simply lacks an annotation.

How to detect outdated Go godoc comments after refactoring?▼

Extract exported symbols and their preceding comment blocks using go/parser or regex fallback, then verify the comment starts with the symbol name and that parameter and return descriptions match the actual signature. Only flag contradictions, not stylistic deviations from Go conventions.

Does this skill automatically fix mismatched code comments?▼

No, it is strictly read-only and never edits source files. Every mismatch is a judgment call between updating the comment or fixing the code, so findings are appended to a memory log with [pending] status markers for human triage.

Can it verify Helm values.yaml comments against chart templates?▼

Yes, it parses values.yaml to enumerate value paths, then searches chart templates for .Values references. It flags orphaned values no template consumes and comments whose claimed defaults disagree with the actual YAML defaults, while skipping known-external patterns like ingress annotations.

What types of comment drift are out of scope for comment verification?▼

Missing comments are out of scope since that belongs to documentation-generation work, as are generated or vendored code, stylistic preferences, and test-code semantics. The skill only flags existing comments that make specific claims contradicted by the code.