Add no-argument interactive mode to fvdb-issue#466
Conversation
When invoked without arguments, fvdb-issue now lists existing issue worktrees from both repos, fetches each issue's title and state from GitHub, and lets the user select one to open in Cursor or close/remove. Also adds a "Workspace" section to the current-issue.md template so agents know they are working in a worktree and should not edit the main repository checkout. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: Mark Harris <mharris@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Mirror the existing "set appropriate labels" guidance from the Issues section into the Pull Requests section so agents apply labels when opening PRs. Signed-off-by: Mark Harris <mharris@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Pull request overview
Adds an interactive “no-argument” mode to fvdb-issue so developers can discover and manage existing issue worktrees across both fvdb-core and fvdb-reality-capture, and updates agent guidance to better reflect the workflow.
Changes:
- Add
fvdb-issueinteractive mode (no args): scan issue worktrees, fetch issue metadata viagh, and offer open/close actions. - Update
fvdb-issuehelp/usage text and enrich the generatedcurrent-issue.mdtemplate with a “Workspace” section. - Fix/extend AI agent contribution guidelines in
AGENTS.md(labeling guidance / formatting).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
devtools/worktree/fvdb-issue |
Implements no-arg interactive listing/management of issue worktrees; updates usage text; adds worktree guidance to generated agent context. |
AGENTS.md |
Adjusts issue/PR guideline bullets (labeling) and fixes formatting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Mark Harris <mharris@nvidia.com>
Signed-off-by: Mark Harris <mharris@nvidia.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Mark Harris <mharris@nvidia.com>
…e-with-no-arguments-should-list
Signed-off-by: Mark Harris <mharris@nvidia.com>
harrism
force-pushed
the
issue-465-fvdb-issue-with-no-arguments-should-list
branch
from
5f75f29 to
16f08ed
Compare
Signed-off-by: Mark Harris <mharris@nvidia.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Use 'git worktree list --porcelain' and parse 'worktree <path>' lines so paths containing spaces are handled correctly. - Replace associative arrays (Bash 4+) with parallel arrays and linear lookup so the script runs on macOS system bash (3.2). Signed-off-by: Mark Harris <mharris@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Fixes #465
When
fvdb-issueis invoked with no arguments, it now:FVDB_CORE_PATHandFVDB_RC_PATHfor directories matching the*-issue-<number>naming patternghfvdb-open) or close/remove it (viafvdb-close)Existing behavior (
fvdb-issue <number>to create a new worktree) is unchanged.Also adds a "Workspace" section to the
current-issue.mdtemplate so AI agents know they are working in a worktree and should not edit the main repository checkout.Also adds a PR label directive to AGENTS.md.
Test plan
fvdb-issuewith no arguments — verify it lists issue worktrees with titles and statusqto cancel — verify clean exito— verify it delegates tofvdb-openc— verify it delegates tofvdb-closefvdb-issue --help— verify updated usage textfvdb-issue <number>— verify existing create-worktree flow is unchangedfvdb-issue— verify "No issue worktrees found" messageMade with Cursor