Files
gastown/internal/formula/formulas/shiny.formula.toml
Raymond Weitekamp 1e76bfd7ce fix: Commit embedded formulas for go install @latest (#117)
* fix: Commit embedded formulas for go install @latest

The internal/formula/formulas/ directory was gitignored, causing
`go install github.com/steveyegge/gastown/cmd/gt@latest` to fail with:

  pattern formulas/*.formula.json: no matching files found

The go:embed directive requires these files at build time, but
go install @latest doesn't run go:generate. By committing the
generated formulas, users can install directly without cloning.

Maintainers should run `go generate ./...` after modifying
.beads/formulas/ to keep the embedded copy in sync.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* ci: Add check for committed embedded formulas

Adds a new CI job that:
1. Builds without running go:generate (catches missing formulas)
2. Verifies committed formulas match .beads/formulas/ source

Also removes redundant go:generate steps from other jobs since
formulas are now committed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* chore: exclude towers-of-hanoi test formulas from embed

These are durability stress test fixtures (pre-computed move sequences),
not production formulas users need. Excluding them reduces embedded
content by ~10K lines.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: gus <steve.yegge@gmail.com>
2026-01-04 23:08:55 -08:00

41 lines
1.4 KiB
TOML

description = "Engineer in a Box - the canonical right way. Design before you code. Review before you ship. Test before you submit."
formula = "shiny"
type = "workflow"
version = 1
[[steps]]
description = "Think carefully about architecture before writing code. Consider: How does this fit into the existing system? What are the edge cases? What could go wrong? Is there a simpler approach?"
id = "design"
title = "Design {{feature}}"
[[steps]]
description = "Write the code for {{feature}}. Follow the design. Keep it simple. Don't gold-plate."
id = "implement"
needs = ["design"]
title = "Implement {{feature}}"
[[steps]]
description = "Review the implementation. Check for: Does it match the design? Are there obvious bugs? Is it readable and maintainable? Are there security concerns?"
id = "review"
needs = ["implement"]
title = "Review implementation"
[[steps]]
description = "Write and run tests. Unit tests for new code, integration tests if needed, run the full test suite, fix any regressions."
id = "test"
needs = ["review"]
title = "Test {{feature}}"
[[steps]]
description = "Submit for merge. Final check: git status, git diff. Commit with clear message. Push and create PR."
id = "submit"
needs = ["test"]
title = "Submit for merge"
[vars]
[vars.assignee]
description = "Who is assigned to this work"
[vars.feature]
description = "The feature being implemented"
required = true