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.1 KiB

hook pre-edit

Execute pre-edit validations and agent assignment before file modifications.

Usage

npx claude-flow hook pre-edit [options]

Options

  • --file, -f <path> - File path to be edited
  • --auto-assign-agent - Automatically assign best agent (default: true)
  • --validate-syntax - Pre-validate syntax before edit
  • --check-conflicts - Check for merge conflicts
  • --backup-file - Create backup before editing

Examples

Basic pre-edit hook

npx claude-flow hook pre-edit --file "src/auth/login.js"

With validation

npx claude-flow hook pre-edit -f "config/database.js" --validate-syntax

Manual agent assignment

npx claude-flow hook pre-edit -f "api/users.ts" --auto-assign-agent false

Safe editing with backup

npx claude-flow hook pre-edit -f "production.env" --backup-file --check-conflicts

Features

Auto Agent Assignment

  • Analyzes file type and content
  • Assigns specialist agents
  • TypeScript → TypeScript expert
  • Database → Data specialist
  • Tests → QA engineer

Syntax Validation

  • Pre-checks syntax validity
  • Identifies potential errors
  • Suggests corrections
  • Prevents broken code

Conflict Detection

  • Checks for git conflicts
  • Identifies concurrent edits
  • Warns about stale files
  • Suggests merge strategies

File Backup

  • Creates safety backups
  • Enables quick rollback
  • Tracks edit history
  • Preserves originals

Integration

This hook is automatically called by Claude Code when:

  • Using Edit or MultiEdit tools
  • Before file modifications
  • During refactoring operations
  • When updating critical files

Manual usage in agents:

# Before editing files
npx claude-flow hook pre-edit --file "path/to/file.js" --validate-syntax

Output

Returns JSON with:

{
  "continue": true,
  "file": "src/auth/login.js",
  "assignedAgent": "auth-specialist",
  "syntaxValid": true,
  "conflicts": false,
  "backupPath": ".backups/login.js.bak",
  "warnings": []
}

See Also

  • hook post-edit - Post-edit processing
  • Edit - File editing tool
  • MultiEdit - Multiple edits tool
  • agent spawn - Manual agent creation