Griffe Check¶
The griffe check implements Layer 5 (Rendering) of docvet's quality model. It captures warnings from the griffe docstring parser to detect issues that would cause broken rendering in mkdocs-material + mkdocstrings documentation sites. 3 rules.
Optional Dependency
The griffe check requires the optional griffe extra:
When griffe is not installed, docvet skips this check gracefully — no error, no finding, just a silent skip.
Rules¶
| Rule ID | Category | Description |
|---|---|---|
griffe-unknown-param |
required | Docstring documents a parameter not in the function signature |
griffe-missing-type |
recommended | Parameter or return value lacks a type annotation in the docstring |
griffe-format-warning |
recommended | Docstring format issue that would break mkdocs rendering |
Catch these early
griffe-unknown-param is the most impactful rule — it catches renamed or removed parameters that still appear in the docstring. These cause visible rendering errors on your docs site.
Example Output¶
Configuration¶
Info
This check has no check-specific configuration. There is no [tool.docvet.griffe] section.
The griffe check parses docstrings using griffe's Google-style parser and captures any warnings emitted during parsing. No thresholds or toggles are needed — if griffe flags it, docvet reports it.
Usage¶
Run the griffe check on your entire codebase:
Check only files with unstaged changes (default):
Check only staged files:
Check specific files:
Add --verbose for file count and timing, or -q to suppress the summary line:
Or run griffe as part of all checks (skipped automatically if griffe is not installed):