write-test-py

Estrelas11

Forks2

Atualizado8 de julho de 2026 às 08:25

Transform the reviewed test stubs into executable test bodies, with the code-quality gate applied here.

Instalação

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ê.

Fonte

nullhack

nullhack/temple8

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	write-test-py
description	Transform the reviewed test stubs into executable test bodies, with the code-quality gate applied here.

Write Test Py

Load [[software-craft/solid]], [[software-craft/object-calisthenics]], [[software-craft/smell-catalogue]], [[software-craft/test-design]] — the quality criteria and body patterns.
Read .cache/<session_id>/journal.md (always present — bootstrapped at plan entry by model-data-schema) and .cache/<session_id>/interview-notes.md. Two rework trigger sources feed the backlog: (a) IF the journal carries escalation findings from build THEN edit the bodies of the contracts it names to match the reworked stubs; (b) IF the interview notes flag findings that MODIFY an existing block THEN edit the bodies of those contracts to match the reworked .pyi. Either source is rework — step 9 re-applies the pending marker. Skip both if neither carries rework.
Write the test bodies — no docstrings, no comments; the body is the spec. Bodies define how entities relate, compose, and collaborate: wire classes, data, and objects following best practices.
Apply the code-quality gate here: SOLID, DRY, KISS, YAGNI, Object Calisthenics per [[software-craft/solid]], [[software-craft/object-calisthenics]]. IF a smell is present THEN reject it per [[software-craft/smell-catalogue]].
Mark each test with the pending marker; the conftest hook skips pending tests so the suite stays green-with-skips until source is built.
Defer the system-under-test import into each test body so an unbuilt module collects cleanly and its pending tests skip rather than error at collection. Keep third-party and test-only imports at module top.
Keep the .py's module-level names and method signatures in exact agreement with its .pyi — stubtest checks the pair strictly.
Run the dev ruff check (ruff check .) on the authored test files; fix every violation so build receives bug-clean tests. Restructure lint (SIM, RUF) and ruff format are merge-time per [[software-craft/docstring-lifecycle]] — do not format here.
Strip docstrings from the test .py you just wrote: uv run python scripts/strip_docstrings.py <authored *_test.py files>.
IF reworking an existing contract THEN edit the body to match the changed .pyi and re-apply the pending marker to the affected tests so they skip until build re-selects them.

Mais deste repositório

mesmo repositório

simulate-contracts

nullhack/temple8

Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.

2026-07-0811

author-test-stubs

nullhack/temple8

Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.

2026-07-0811

interview-building-blocks

nullhack/temple8

Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.

2026-07-0811

interview-general

nullhack/temple8

Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.

2026-07-0811

merge-to-dev

nullhack/temple8

Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.

2026-07-0811

publish-release

nullhack/temple8

Publish the delivered batch as release notes, a PR to main, or a tagged release.

2026-07-0811

Write Test Py

Load [[software-craft/solid]], [[software-craft/object-calisthenics]], [[software-craft/smell-catalogue]], [[software-craft/test-design]] — the quality criteria and body patterns.

Read .cache/<session_id>/journal.md (always present — bootstrapped at plan entry by model-data-schema) and .cache/<session_id>/interview-notes.md. Two rework trigger sources feed the backlog: (a) IF the journal carries escalation findings from build THEN edit the bodies of the contracts it names to match the reworked stubs; (b) IF the interview notes flag findings that MODIFY an existing block THEN edit the bodies of those contracts to match the reworked .pyi. Either source is rework — step 9 re-applies the pending marker. Skip both if neither carries rework.

Write the test bodies — no docstrings, no comments; the body is the spec. Bodies define how entities relate, compose, and collaborate: wire classes, data, and objects following best practices.

Apply the code-quality gate here: SOLID, DRY, KISS, YAGNI, Object Calisthenics per [[software-craft/solid]], [[software-craft/object-calisthenics]]. IF a smell is present THEN reject it per [[software-craft/smell-catalogue]].

Mark each test with the pending marker; the conftest hook skips pending tests so the suite stays green-with-skips until source is built.

Defer the system-under-test import into each test body so an unbuilt module collects cleanly and its pending tests skip rather than error at collection. Keep third-party and test-only imports at module top.

Keep the .py's module-level names and method signatures in exact agreement with its .pyi — stubtest checks the pair strictly.

Run the dev ruff check (ruff check .) on the authored test files; fix every violation so build receives bug-clean tests. Restructure lint (SIM, RUF) and ruff format are merge-time per [[software-craft/docstring-lifecycle]] — do not format here.

Strip docstrings from the test .py you just wrote: uv run python scripts/strip_docstrings.py <authored *_test.py files>.

IF reworking an existing contract THEN edit the body to match the changed .pyi and re-apply the pending marker to the affected tests so they skip until build re-selects them.