SETI/rms-oops

bug-report

Standards for writing clear, reproducible bug reports, covering required components, severity levels, evidence, and environment details. Use when the user asks to write, file, or review a bug report or issue.

원문 언어: 영어

critique-documentation

Analyze a project's documentation (README, user guide, developer guide, how-to articles, docstrings, and Sphinx setup) against the project's documentation rules and produce a report (no edits). Use when the user asks to critique, review, or audit the…

원문 언어: 영어

critique-test-suite

Analyze the test suite for consistency, completeness, redundancy, parallel safety, and assertion quality. Produces a comprehensive report (no test modifications). Use when the user asks to critique tests, review the test suite, or generate a report for fixing…

원문 언어: 영어

git-workflow

Commit message format, branch naming, and the pull request workflow for this project. Use when the user asks to commit, name a branch, or prepare changes for review.

원문 언어: 영어

pull-request

Standards for pull request structure, covering purpose, implementation details, testing evidence, and the review checklist. Use when the user asks to write a pull request description, open a PR, or review one.

원문 언어: 영어

python-codebase-analysis

Analyzes a Python codebase and produces high-level recommendations for restructuring, refactoring, and alignment with modern best practices. Use when the user asks to analyze the codebase, audit code quality, suggest improvements, refactoring ideas, or assess…

원문 언어: 영어

run-all-checks

Run all linting, type checking, tests, Markdown lint, and documentation build for the project. Check for errors and warnings, then fix any problems found. Use when the user asks to run checks, verify the build, run CI locally, or fix lint/type/test errors.

원문 언어: 영어