MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-04-02 17:31:05 -07:00
Code Issues Packages Projects Releases Wiki Activity

feat(core): enhance tracker task schemas for detailed titles and descriptions (#23902)

Browse Source
This commit is contained in:
anj-s
2026-04-01 10:19:47 -07:00
committed by GitHub
parent bf3ac20da0
commit 3a32d9723e
4 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/core/src/core/__snapshots__/prompts.test.ts.snap
View File

@@ -2908,6 +2908,7 @@ You are operating with a persistent file-based task tracking system located at \
5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence).
6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating.
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.
8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.
# Operational Guidelines
@@ -3087,6 +3088,7 @@ You are operating with a persistent file-based task tracking system located at \
5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence).
6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating.
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.
8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.
# Operational Guidelines

3
packages/core/src/prompts/snippets.legacy.ts
View File

@@ -502,7 +502,8 @@ You are operating with a persistent file-based task tracking system located at \
4. **PLAN MODE INTEGRATION**: If an approved plan exists, you MUST use the \`${TRACKER_CREATE_TASK_TOOL_NAME}\` tool to decompose it into discrete tasks before writing any code. Maintain a bidirectional understanding between the plan document and the task graph.
5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence).
6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating.
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.`.trim();
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.
8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.`.trim();
}
// --- Leaf Helpers (Strictly strings or simple calls) ---

3
packages/core/src/prompts/snippets.ts
View File

@@ -552,7 +552,8 @@ You are operating with a persistent file-based task tracking system located at \
4. **PLAN MODE INTEGRATION**: If an approved plan exists, you MUST use the ${trackerCreate} tool to decompose it into discrete tasks before writing any code. Maintain a bidirectional understanding between the plan document and the task graph.
5. **VERIFICATION**: Before marking a task as complete, verify the work is actually done (e.g., run the test, check the file existence).
6. **STATE OVER CHAT**: If the user says "I think we finished that," but the tool says it is 'pending', trust the tool--or verify explicitly before updating.
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.`.trim();
7. **DEPENDENCY MANAGEMENT**: Respect task topology. Never attempt to execute a task if its dependencies are not marked as 'closed'. If you are blocked, focus only on the leaf nodes of the task graph.
8. **DETAILED TASKS**: Ensure that the tasks created have highly detailed titles and descriptions. The description MUST provide significantly more specific details and technical context than the title.`.trim();
}
export function renderPlanningWorkflow(

8
packages/core/src/tools/definitions/trackerTools.ts
View File

@@ -23,11 +23,13 @@ export const TRACKER_CREATE_TASK_DEFINITION: ToolDefinition = {
properties: {
title: {
type: 'string',
description: 'Short title of the task.',
description:
'Detailed title of the task. Should be concise but provide enough detail to understand the objective.',
},
description: {
type: 'string',
description: 'Detailed description of the task.',
description:
'Detailed description of the task. Must contain more specific details and context than the title.',
},
type: {
type: 'string',
@@ -66,7 +68,7 @@ export const TRACKER_UPDATE_TASK_DEFINITION: ToolDefinition = {
},
description: {
type: 'string',
description: 'New description for the task.',
description: 'New detailed description for the task.',
},
status: {
type: 'string',