chore(openspec): config.yaml context has no one-test commands for the review

Open Beginner friendly
#362 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
tooling

Research direction

Read openspec/config.yaml and inspect the repository’s Go tests and .txtar scripts under test/integration/testdata to confirm the runner commands described in the issue. Add those one-test commands to the context field. Done when sb:openspec-review can read both command patterns from that field.

Written by the indexing model from the issue text.

Description

chore needs-triage
What kind of chore?

Repository housekeeping

What needs doing?

Add the repository's one-test commands to the context field of openspec/config.yaml.

sb:openspec-review runs each covering test of an implementation review with the one-test command for that test's runner. It reads those commands from context. The field has none today, so every review round has to work out the commands again.

The repository has two runners:

  • A Go test: go test -count=1 -run '^<Name>$' ./<package>
  • A .txtar script under test/integration/testdata: go test -count=1 -run '^TestScripts/<basename without .txtar>$' ./test/integration

/sb:openspec-review-setup --with-context can record them.

Why now?

The c-include-resolution review (#361) ran six implementation rounds. Each round needed the same command mapping, built by hand.

🤖 Generated with Claude Code

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.