Task Description
Currently, the "View Prompt" button in the Task Details view of the GitFix UI works correctly for standard issue processing tasks. However, this functionality is missing for PR comment followup tasks.
The goal of this task is to enable the "View Prompt" feature for these followup tasks to achieve feature parity and improve debuggability.
The Problem
The root cause is that the processPullRequestCommentJob in src/worker.js does not include the claudeResult object in its return value upon completion. The dashboard's backend API (/api/task/:taskId/history) relies on this return value being present in the completed BullMQ job data to reconstruct the task's history. Without it, the frontend TaskDetails.jsx component never receives the sessionId or conversationId needed to fetch and display the prompt.
Implementation Steps
-
Modify src/worker.js:
- Locate the
processPullRequestCommentJob function.
- Find the final
return statement within the main try block.
- Update the returned object to include the
claudeResult, which is already available in the function's scope. This should apply to both successful runs (with or without code changes).
-
Verification:
- No backend or frontend code changes should be necessary beyond the worker modification.
- After implementing the change, trigger a PR comment followup task.
- Navigate to the Task Details view for that task in the GitFix UI.
- Confirm that a "View Prompt" button appears in the
CLAUDE_EXECUTION or CLAUDE_COMPLETED history step.
- Click the button and verify that the correct LLM prompt is displayed in a modal window.
Task Description
Currently, the "View Prompt" button in the Task Details view of the GitFix UI works correctly for standard issue processing tasks. However, this functionality is missing for PR comment followup tasks.
The goal of this task is to enable the "View Prompt" feature for these followup tasks to achieve feature parity and improve debuggability.
The Problem
The root cause is that the
processPullRequestCommentJobinsrc/worker.jsdoes not include theclaudeResultobject in its return value upon completion. The dashboard's backend API (/api/task/:taskId/history) relies on this return value being present in the completed BullMQ job data to reconstruct the task's history. Without it, the frontendTaskDetails.jsxcomponent never receives thesessionIdorconversationIdneeded to fetch and display the prompt.Implementation Steps
Modify
src/worker.js:processPullRequestCommentJobfunction.returnstatement within the maintryblock.claudeResult, which is already available in the function's scope. This should apply to both successful runs (with or without code changes).Verification:
CLAUDE_EXECUTIONorCLAUDE_COMPLETEDhistory step.