Repository navigation
feat: agent work loop (issues, next, note) and a live dashboard - #5
Merged
Merged
Conversation
An agent fixing findings had no way to ask the tracker what to work on, so it picked its own order, which is not the one the person watching the dashboard sees. - `qa-tracker issues` lists issues in the dashboard's order (open: severity, then complexity) with --status/--severity/--feature/--category filters. - `qa-tracker next` returns the open issue to work on now: the top of that order, with its details and source. - `qa-tracker note <issue> <text…>` appends a dated paragraph to the details; words need no quoting and --file reads the text, so notes survive shells that mangle multi-line arguments. - The dashboard polls GET /api/version and reloads when the data files change, unless someone is editing, so a watcher sees CLI and agent writes land. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9f4f5fd7b5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…e config Review feedback on the live dashboard: - An edit's follow-up GET /api/version could adopt a CLI or agent write that landed in between as the page's own, so the page never reloaded for it. POST /api/edit now answers with the data version just before and just after the commit; the page adopts the new one only when the "before" version is the one it had, and otherwise treats itself as stale. - dataVersion no longer includes qa-tracker.config.json: serve reads the config once at start, so a config-triggered reload still showed the old title and categories. The README says to restart serve after a config edit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
An agent fixing findings had no way to ask the tracker what to work on next, so it picked its own order — not the one the person watching the dashboard sees. This adds a small work loop and makes the dashboard follow writes made elsewhere.
qa-tracker issues— issues in the dashboard's order (open: severity, then complexity; unset last), with--status open|fixed|verified-fixed|wont-fix|closed|all,--severity,--feature,--categoryand--json.qa-tracker next— the open issue to work on now (the top of that order), with its details and source, plus a hint for closing it.qa-tracker note <issue> <text…>— appends a dated paragraph to the issue's details. The words need no quoting and--file <path>reads the text, so notes survive shells that mangle multi-line arguments (e.g. Windows.cmdshims).GET /api/version(size + mtime of the data files) every 3 s and reloads when the CLI or an agent wrote; while in Edit mode or with a field focused it only says the data changed. Its own saves re-sync the version, so they don't count as outside changes.listIssues,nextIssue,formatIssueLine,appendNote,dataVersion. No schema change; existing trackers are untouched.initAGENTS.md template ("Fixing findings"), the skill, CHANGELOG.Tests
npm run check: 191/191 pass (newtest/work.test.mjs, two CLI tests for the loop andnote --file, one server test for/api/version), demo tracker validates.🤖 Generated with Claude Code