95c299df64
* move claude rules and commands to assets/claude * update claude profile to copy assets/claude to .claude * fix formatting * feat(profiles): Implement unified profile system - Convert Claude and Codex profiles to use createProfile() factory - Remove simple vs complex profile distinction in rule transformer - Unify convertAllRulesToProfileRules() to handle all profiles consistently - Fix mcpConfigPath construction in base-profile.js for null mcpConfigName - Update terminology from 'simpleProfiles' to 'assetOnlyProfiles' throughout - Ensure Claude .claude directory copying works in both CLI and MCP contexts - All profiles now follow same execution flow with proper lifecycle functions Changes: - src/profiles/claude.js: Convert to createProfile() factory pattern - src/profiles/codex.js: Convert to createProfile() factory pattern - src/utils/rule-transformer.js: Unified profile handling logic - src/utils/profiles.js: Remove simple profile categorization - src/profiles/base-profile.js: Fix mcpConfigPath construction - scripts/modules/commands.js: Update variable naming - tests/: Update all tests for unified system and terminology Fixes Claude profile asset copying issue in MCP context. All tests passing (617 passed, 11 skipped). * re-checkin claude files * fix formatting * chore: clean up test Claude rules files * chore: add changeset for unified profile system * add claude files back * add changeset * restore proper gitignore * remove claude agents file from root * remove incorrect doc * simplify profiles and update tests * update changeset * update changeset * remove profile specific code * streamline profiles with defaults and update tests * update changeset * add newline at end of gitignore * restore changes * streamline profiles with defaults; update tests and add vscode test * update rule profile tests * update wording for clearer profile management * refactor and clarify terminology * use original projectRoot var name * revert param desc * use updated claude assets from neno * add "YOUR_" before api key here * streamline codex profile * add gemini profile * update gemini profile * update tests * relocate function * update rules interactive setup Gemini desc * remove duplicative code * add comma
97 lines
2.2 KiB
Markdown
97 lines
2.2 KiB
Markdown
Advanced project analysis with actionable insights and recommendations.
|
|
|
|
Arguments: $ARGUMENTS
|
|
|
|
## Comprehensive Project Analysis
|
|
|
|
Multi-dimensional analysis based on requested focus area.
|
|
|
|
### 1. **Analysis Modes**
|
|
|
|
Based on $ARGUMENTS:
|
|
- "velocity" → Sprint velocity and trends
|
|
- "quality" → Code quality metrics
|
|
- "risk" → Risk assessment and mitigation
|
|
- "dependencies" → Dependency graph analysis
|
|
- "team" → Workload and skill distribution
|
|
- "architecture" → System design coherence
|
|
- Default → Full spectrum analysis
|
|
|
|
### 2. **Velocity Analytics**
|
|
|
|
```
|
|
📊 Velocity Analysis
|
|
━━━━━━━━━━━━━━━━━━━
|
|
Current Sprint: 24 points/week ↗️ +20%
|
|
Rolling Average: 20 points/week
|
|
Efficiency: 85% (17/20 tasks on time)
|
|
|
|
Bottlenecks Detected:
|
|
- Code review delays (avg 4h wait)
|
|
- Test environment availability
|
|
- Dependency on external team
|
|
|
|
Recommendations:
|
|
1. Implement parallel review process
|
|
2. Add staging environment
|
|
3. Mock external dependencies
|
|
```
|
|
|
|
### 3. **Risk Assessment**
|
|
|
|
**Technical Risks**
|
|
- High complexity tasks without backup assignee
|
|
- Single points of failure in architecture
|
|
- Insufficient test coverage in critical paths
|
|
- Technical debt accumulation rate
|
|
|
|
**Project Risks**
|
|
- Critical path dependencies
|
|
- Resource availability gaps
|
|
- Deadline feasibility analysis
|
|
- Scope creep indicators
|
|
|
|
### 4. **Dependency Intelligence**
|
|
|
|
Visual dependency analysis:
|
|
```
|
|
Critical Path:
|
|
#12 → #15 → #23 → #45 → #50 (20 days)
|
|
↘ #24 → #46 ↗
|
|
|
|
Optimization: Parallelize #15 and #24
|
|
Time Saved: 3 days
|
|
```
|
|
|
|
### 5. **Quality Metrics**
|
|
|
|
**Code Quality**
|
|
- Test coverage trends
|
|
- Complexity scores
|
|
- Technical debt ratio
|
|
- Review feedback patterns
|
|
|
|
**Process Quality**
|
|
- Rework frequency
|
|
- Bug introduction rate
|
|
- Time to resolution
|
|
- Knowledge distribution
|
|
|
|
### 6. **Predictive Insights**
|
|
|
|
Based on patterns:
|
|
- Completion probability by deadline
|
|
- Resource needs projection
|
|
- Risk materialization likelihood
|
|
- Suggested interventions
|
|
|
|
### 7. **Executive Dashboard**
|
|
|
|
High-level summary with:
|
|
- Health score (0-100)
|
|
- Top 3 risks
|
|
- Top 3 opportunities
|
|
- Recommended actions
|
|
- Success probability
|
|
|
|
Result: Data-driven decisions with clear action paths. |