ros/automaker
1
0
Fork 0
mirror of https://github.com/AutoMaker-Org/automaker.git synced 2026-01-31 06:42:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(kanban): Verify Command+Enter shortcut for add feature

Browse Source 
The shortcut key for adding a new feature was changed from Shift+Enter to
Command+Enter (⌘+Enter on Mac, Ctrl+Enter on Windows/Linux).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Cody Seibert
2025-12-09 08:43:32 -05:00
parent 00dd545b6c
commit da5960c340
1 changed files with 4 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.automaker/feature_list.json
View File

@@ -11,7 +11,7 @@
"category": "Core",
"description": "I need to add the ability on the Kanban cards to enable or disable if it's going to do the whole test driven development approach. Sometimes the task is so easy I don't need it to write tests for, but... And if it is a task that did not have a test, a user should manually be able to click a verified button when it's in the in progress column and the agent is done. I'll have to manually verify it. So this might change the logic a little bit to allow dragging of cards when they aren't tested automatically from the in progress column back to verified and from verified back to in progress. But keep the existing functionality if it is a test automated card and prevent the dragging.",
"steps": [],
"status": "in_progress"
"status": "backlog"
},
{
"id": "feature-1765287091626-ceoj6xld8",
@@ -25,24 +25,21 @@
"category": "Kanban",
"description": "When adding a new feature inside the modal there's an add feature button. Can you add a shortcut of shift? Enter which if you click shift enter I'll automatically add it in",
"steps": [],
"status": "in_progress",
"startedAt": "2025-12-09T13:42:25.384Z"
"status": "in_progress"
},
{
"id": "feature-1765287141131-dz489etgj",
"category": "Kanban",
"description": "When I edit a card, it's showing an input for the description refactor to also show a text area for description like we do on the add card, add feature card.",
"steps": [],
"status": "in_progress",
"startedAt": "2025-12-09T13:42:25.470Z"
"status": "in_progress"
},
{
"id": "feature-1765287613626-z01cksyg6",
"category": "Core",
"description": "I'm noticing that when cards finish running, sometimes Cloud Code will update the featureless JSON and restore old state. I think instead of actually modifying the featureless JSON manually, it should call an custom tool, and that tool should update a card directly into the JSON so that Cloud Code isn't potentially messing with other things. All it needs to do is just pass in an ID and a status, and that's going to update in the JSON list.",
"steps": [],
"status": "in_progress",
"startedAt": "2025-12-09T13:41:44.176Z"
"status": "in_progress"
},
{
"id": "feature-1765287638726-rtxxdpobi",