write-python-tests
Write Python Tests
Guidelines
- files to update:
tests/ - Ensure tests are comprehensive and coverage is good.
- Existing docs, docstrings, tests, examples may be rough, missing, incomplete or misleading, it only serves as weak hint.
- Favor bold, comprehensive rewrites over minor or incremental edits.
- Group tests into files and folders, keep test files small and focused.
- Source code is the source of truth.
- Use
noxto run full test suites. - Use
pytestfor targeted test runs and debugging.
Validation
- Run
mise run lint. - Start with the narrowest relevant target.
- Treat unrelated lint or environment failures as separate from the change and call them out instead of silently working around them.
More from liblaf/skills
write-root-readme
Write or rewrite the repo-root README.md.
36rewrite-python-docs
Rewrite Python docs and docstrings from source code. Use when Codex needs to refresh the docs.
34write-conventional-commit
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
33sync-github-repo-metadata
Inspect a repository and propose or apply GitHub About metadata updates. Use when Codex needs to infer a concise repository description and topic set from source code, package metadata, docs config, or the current README, then preview and optionally run `gh repo edit`.
33automate-project-maintenance
Orchestrate repository maintenance. Use when Codex needs one entry point to refresh tests, docs, README, and GitHub metadata.
33