Add a single-command `make check` validation loop to templates/
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- build-system, testing
Research direction
Start in templates/Makefile by reading the existing lint, vet, test, generate-check, frontend-lint, frontend-typecheck, and frontend-audit targets and their dependencies. Add the aggregate check target in a sensible verification order, then update templates/AGENTS.md to document it. Done means make check runs the backend and frontend checks successfully on a generated project.
Written by the indexing model from the issue text.
Description
Generated projects have no aggregate verification target. Validation today is lefthook's pre-commit chain plus separate make lint, vet, test, generate-check, frontend-lint, frontend-typecheck and frontend-audit targets.
That is a menu, and agents given a menu reliably run fewer checks than they should. roadmap.md already refers to make check in two places (the Agent Guardrails (Claude) and Static Analysis rows) as if it exists; it does not.
Ask: one check target in templates/Makefile running the backend and frontend verification steps in a sensible order, so there is a single command an agent (or a human, or CI) can run to know the tree is good.
Follow-up: templates/AGENTS.md — introduced by #13 — documents the individual targets until this lands, and should name make check once it does.
Surfaced while designing #13. See docs/superpowers/specs/2026-09-04-selectable-agent-guardrails-design.md (Out of scope).
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 3h 1m
- Merged PRs (30d)
- 29
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dennys-bd/gonext
-
idea tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
core-foundation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
core-foundation enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
core-foundation idea
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement framework-gap
Difficulty 3/5 1-2 days Newbie friendliness 76/100
All issues in dennys-bd/gonext
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100