chore(openspec): config.yaml context has no one-test commands for the review
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
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
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
.txtarscript undertest/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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 seanb4t/codegraph-go
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
seanb4t/codegraph-go#380 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#379 ·
Maintainers usually reply within 1 day
-
area:query bug priority:low spec-needed
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
seanb4t/codegraph-go#355 ·
Maintainers usually reply within 1 day
-
area:ci chore priority:low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
seanb4t/codegraph-go#329 ·
Maintainers usually reply within 1 day
All issues in seanb4t/codegraph-go
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day