chess/.claude/commands/hooks/post-task.md
Christoph Wagner 5ad0700b41 refactor: Consolidate repository structure - flatten from workspace pattern
Restructured project from nested workspace pattern to flat single-repo layout.
This eliminates redundant nesting and consolidates all project files under version control.

## Migration Summary

**Before:**
```
alex/ (workspace, not versioned)
├── chess-game/ (git repo)
│   ├── js/, css/, tests/
│   └── index.html
└── docs/ (planning, not versioned)
```

**After:**
```
alex/ (git repo, everything versioned)
├── js/, css/, tests/
├── index.html
├── docs/ (project documentation)
├── planning/ (historical planning docs)
├── .gitea/ (CI/CD)
└── CLAUDE.md (configuration)
```

## Changes Made

### Structure Consolidation
- Moved all chess-game/ contents to root level
- Removed redundant chess-game/ subdirectory
- Flattened directory structure (eliminated one nesting level)

### Documentation Organization
- Moved chess-game/docs/ → docs/ (project documentation)
- Moved alex/docs/ → planning/ (historical planning documents)
- Added CLAUDE.md (workspace configuration)
- Added IMPLEMENTATION_PROMPT.md (original project prompt)

### Version Control Improvements
- All project files now under version control
- Planning documents preserved in planning/ folder
- Merged .gitignore files (workspace + project)
- Added .claude/ agent configurations

### File Updates
- Updated .gitignore to include both workspace and project excludes
- Moved README.md to root level
- All import paths remain functional (relative paths unchanged)

## Benefits

 **Simpler Structure** - One level of nesting removed
 **Complete Versioning** - All documentation now in git
 **Standard Layout** - Matches open-source project conventions
 **Easier Navigation** - Direct access to all project files
 **CI/CD Compatible** - All workflows still functional

## Technical Validation

-  Node.js environment verified
-  Dependencies installed successfully
-  Dev server starts and responds
-  All core files present and accessible
-  Git repository functional

## Files Preserved

**Implementation Files:**
- js/ (3,517 lines of code)
- css/ (4 stylesheets)
- tests/ (87 test cases)
- index.html
- package.json

**CI/CD Pipeline:**
- .gitea/workflows/ci.yml
- .gitea/workflows/release.yml

**Documentation:**
- docs/ (12+ documentation files)
- planning/ (historical planning materials)
- README.md

**Configuration:**
- jest.config.js, babel.config.cjs, playwright.config.js
- .gitignore (merged)
- CLAUDE.md

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

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-23 10:05:26 +01:00

2.2 KiB

hook post-task

Execute post-task cleanup, performance analysis, and memory storage.

Usage

npx claude-flow hook post-task [options]

Options

  • --task-id, -t <id> - Task identifier for tracking
  • --analyze-performance - Generate performance metrics (default: true)
  • --store-decisions - Save task decisions to memory
  • --export-learnings - Export neural pattern learnings
  • --generate-report - Create task completion report

Examples

Basic post-task hook

npx claude-flow hook post-task --task-id "auth-implementation"

With full analysis

npx claude-flow hook post-task -t "api-refactor" --analyze-performance --generate-report

Memory storage

npx claude-flow hook post-task -t "bug-fix-123" --store-decisions --export-learnings

Quick cleanup

npx claude-flow hook post-task -t "minor-update" --analyze-performance false

Features

Performance Analysis

  • Measures execution time
  • Tracks token usage
  • Identifies bottlenecks
  • Suggests optimizations

Decision Storage

  • Saves key decisions made
  • Records implementation choices
  • Stores error resolutions
  • Maintains knowledge base

Neural Learning

  • Exports successful patterns
  • Updates coordination models
  • Improves future performance
  • Trains on task outcomes

Report Generation

  • Creates completion summary
  • Documents changes made
  • Lists files modified
  • Tracks metrics achieved

Integration

This hook is automatically called by Claude Code when:

  • Completing a task
  • Switching to a new task
  • Ending a work session
  • After major milestones

Manual usage in agents:

# In agent coordination
npx claude-flow hook post-task --task-id "your-task-id" --analyze-performance true

Output

Returns JSON with:

{
  "taskId": "auth-implementation",
  "duration": 1800000,
  "tokensUsed": 45000,
  "filesModified": 12,
  "performanceScore": 0.92,
  "learningsExported": true,
  "reportPath": "/reports/task-auth-implementation.md"
}

See Also

  • hook pre-task - Pre-task setup
  • performance report - Detailed metrics
  • memory usage - Memory management
  • neural patterns - Pattern analysis