Conversation
Register nextTask and completeTask commands in package.json to support keyboard-driven workflow through the task list. Made-with: Cursor
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 25c9f7c310
ℹ️ 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".
| "category": "Workday" | ||
| }, | ||
| { | ||
| "command": "workday.nextTask", |
There was a problem hiding this comment.
Register handlers for newly contributed commands
The new workday.nextTask/workday.completeTask entries are added to the command palette, but there are no matching vscode.commands.registerCommand(...) calls for these IDs in src/extension.ts (only workday.synthesize, workday.openSettings, workday.resetOnboarding, and workday.setSlackToken are registered). In practice, triggering either new command from the palette or a keybinding will fail with a command-not-found error, so the feature introduced by this commit is currently unusable.
Useful? React with 👍 / 👎.
Summary
workday.nextTaskcommand to focus the next task in the listworkday.completeTaskcommand to mark the current task as doneTest plan