mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-05 01:50:27 +08:00

Files

catlog22 ff1ca34c2e refactor: Streamline intelligent tools strategy with unified template system

Major Changes:
- Merge tools-implementation-guide.md into intelligent-tools-strategy.md
- Consolidate TEMPLATE and RULES fields into single RULES field
- Standardize template references using $(cat ...) format
- Reduce document length by 66% (520→177 lines) while preserving core functionality

Template System Improvements:
- Universal 4-field command format: PURPOSE | TASK | EXPECTED | RULES
- Unified rules format: $(cat template.txt) | constraints
- Comprehensive template directory structure with examples
- Cross-tool template compatibility and reuse patterns

Content Optimization:
- Remove redundant examples and duplicate content
- Focus on universal command templates and common scenarios
- Simplify tool selection matrix with clear task-to-tool mapping
- Streamline workflow integration with essential best practices

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

Co-Authored-By: Claude <noreply@anthropic.com>

2025-09-17 23:17:31 +08:00

4.5 KiB

Raw Blame History

name, description, usage, argument-hint, examples, allowed-tools, model

name

description

usage

argument-hint

examples

allowed-tools

model

execute

Auto-execution of implementation tasks with YOLO permissions and intelligent context inference

/gemini:execute <description|task-id>

implementation description or task-id

/gemini:execute "implement user authentication system"

/gemini:execute "optimize React component performance"

/gemini:execute IMPL-001

/gemini:execute "fix API performance issues"

Bash(gemini:*)

sonnet

Gemini Execute Command (/gemini:execute)

Overview

⚡ YOLO-enabled execution: Auto-approves all confirmations for streamlined implementation workflow.

Purpose: Execute implementation tasks using intelligent context inference and Gemini CLI with full permissions.

Core Guidelines: @~/.claude/workflows/intelligent-tools-strategy.md

🚨 YOLO Permissions

All confirmations auto-approved by default:

✅ File pattern inference confirmation
✅ Gemini execution confirmation
✅ File modification confirmation
✅ Implementation summary generation

Execution Modes

1. Description Mode

Input: Natural language description

/gemini:execute "implement JWT authentication with middleware"

Process: Keyword analysis → Pattern inference → Context collection → Execution

2. Task ID Mode

Input: Workflow task identifier

/gemini:execute IMPL-001

Process: Task JSON parsing → Scope analysis → Context integration → Execution

Context Inference Logic

Auto-selects relevant files based on:

Keywords: "auth" → @{**/*auth*,**/*user*}
Technology: "React" → @{src/**/*.{jsx,tsx}}
Task Type: "api" → @{**/api/**/*,**/routes/**/*}
Always includes: @{CLAUDE.md,**/*CLAUDE.md}

Command Options

Option	Purpose
`--debug`	Verbose execution logging
`--save-session`	Save complete execution session to workflow

Workflow Integration

Session Management

⚠️ Auto-detects active session: Checks .workflow/.active-* marker file

Session storage:

Active session exists: Saves to .workflow/WFS-[topic]/.chat/execute-[timestamp].md
No active session: Creates new session directory

Task Integration

# Execute specific workflow task
/gemini:execute IMPL-001

# Loads from: .task/IMPL-001.json
# Uses: task context, brainstorming refs, scope definitions
# Updates: workflow status, generates summary

Execution Templates

User Description Template

gemini --all-files -p "@{inferred_patterns} @{CLAUDE.md,**/*CLAUDE.md}

Implementation Task: [user_description]

Provide:
- Specific implementation code
- File modification locations (file:line)
- Test cases
- Integration guidance"

Task ID Template

gemini --all-files -p "@{task_files} @{brainstorming_refs} @{CLAUDE.md,**/*CLAUDE.md}

Task: [task_title] (ID: [task-id])
Type: [task_type]
Scope: [task_scope]

Execute implementation following task acceptance criteria."

Auto-Generated Outputs

1. Implementation Summary

Location: .summaries/[TASK-ID]-summary.md or auto-generated ID

# Task Summary: [Task-ID] [Description]

## Implementation
- **Files Modified**: [file:line references]
- **Features Added**: [specific functionality]
- **Context Used**: [inferred patterns]

## Integration
- [Links to workflow documents]

2. Execution Session

Location: .chat/execute-[timestamp].md

# Execution Session: [Timestamp]

## Input
[User description or Task ID]

## Context Inference
[File patterns used with rationale]

## Implementation Results
[Generated code and modifications]

## Status Updates
[Workflow integration updates]

Error Handling

Task ID not found: Lists available tasks
Pattern inference failure: Uses generic src/**/* pattern
Execution failure: Attempts fallback with simplified context
File modification errors: Reports specific file/permission issues

Performance Features

Smart caching: Frequently used pattern mappings
Progressive inference: Precise → broad pattern fallback
Parallel execution: When multiple contexts needed
Directory optimization: Switches to optimal execution path

Integration Workflow

Typical sequence:

workflow:plan → Creates tasks
/gemini:execute IMPL-001 → Executes with YOLO permissions
Auto-updates workflow status and generates summaries
workflow:review → Final validation

vs. /gemini:analyze: Execute performs analysis and implementation, analyze is read-only.

4.5 KiB Raw Blame History