Skip to content
StellarFirmStellarFirm

Prompt libraryCoderAdd tests for one module

Coding sessionSkill · write-tests

Add tests for one module

Add tests for one module with the repository's own runner. No pull request unless you ask for one.

Layer 01

What you say to StellarFirm

Write tests for the parser.

Layer 02

What StellarFirm tells the coding session

Add tests for the parser using the framework and layout this repository already has (see AGENTS.md). Do not add a new test runner. Test behaviour, not implementation details. No network calls or live credentials.

Run the suite and report the result honestly, including skipped or flaky tests.

Edit the working tree only. Do not commit, push, merge, or switch away from the current branch.

Do not open a pull request unless the CEO asked for one. If they did, wait for Approve, then publish a new stellarfirm/coder/<slug>-<job> branch with git push -u origin (never force) and open a draft pull request.

Never merge. Never force-push. Never push the default branch. Do not use subscription-login tokens.

Back to the Coder library