Menu
Check code style against SUEWS conventions. Complements ruff/fprettify.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Review SUEWS PRs. Drafts comments for approval before posting.
Use whenever the user wants to fix a SUEWS GitHub issue into a validated, PR-ready branch. Trigger for requests like "fix issue
Use whenever auditing, clarifying, rewriting, labelling, or batch-reviewing SUEWS GitHub issues so they become maintainer-ready. Trigger for requests like "audit this issue", "make this issue agent-ready", "rewrite issue
Use whenever auditing, prioritising, or batch-triaging SUEWS draft and stalled pull requests so each gets a clear disposition. Trigger for "triage PRs", "which draft PRs need attention", "what's the disposition of these PRs", "groom the PR backlog", "defer this PR with a reason", "which PRs are ready to advance to merge", or a scheduled PR-backlog sweep. Routes live PRs to prep-pr/split-pr/queue-pr; defers or escalates the rest; never merges or closes.
Prepare SUEWS release with pre-flight checks and tag generation.
Documentation sanity check for SUEWS source files. Two checks under one roof - non-ASCII characters in sphinx-gallery tutorials/RST/docstrings (with context-aware RST/LaTeX/matplotlib replacement), and bibliography topic-tag convention plus metadata backfill on the refs bib files. Use when editing docs/source files or the refs-*.bib files, when a doc hook flags an issue, or when asked to "audit docs", "check docs", "fix non-ASCII", "check bib tags", "curate refs". Complements sync-docs (doc-code content consistency) and lint-code (code style).
Baseado na classificação ocupacional SOC
| name | lint-code |
| description | Check code style against SUEWS conventions. Complements ruff/fprettify. |
Check code against project conventions in .claude/rules/.
ruff check, fprettify --diffruff check --select D to
surface numpy-style docstring violations (the global ruff check already
enforces D, but this scoped call keeps docstring findings separated in
the report).
git diff --name-only origin/master...HEAD -- '*.py'[lint.per-file-ignores] in .ruff.toml (seeded
from the whole repo, not just src/supy/); any finding reported here is
new debt introduced on this branch..claude/rules/| Type | Rules |
|---|---|
| Fortran | .claude/rules/fortran/conventions.md |
| Python | .claude/rules/python/conventions.md |
| RST | .claude/rules/docs/conventions.md |
| CHANGELOG | .claude/rules/changelog/format.md |
[code-style] Analysis
=== Fortran ===
file.f95:L12: issue description
=== Python ===
file.py:L23: issue description
=== Docstrings ===
file.py:L23: Dxxx description (numpy-style rule)
Summary: N files, M issues
If a changed file still shows docstring findings after a good-faith fix, check whether
the file is in [lint.per-file-ignores] in .ruff.toml — if so, either (a) finish
cleaning it and remove its entry from that table, or (b) leave it alone (existing debt).
.claude/rules/ - Full conventions (auto-loaded)references/quick-checks.md - Common issues.py tutorials (comment -> RST,
print -> terminal, matplotlib -> LaTeX), use the audit-docs skill, which
carries the context-specific replacement rules.