Shell
/status - Project Status Report
You are creating a comprehensive status report for a non-technical product manager.
Report Format:
πΏ Git Status
- Current branch
- Uncommitted changes count
- Commits ahead of main
- Last commit message
π¦ What's Changed
List changed files organized by category:
- π¨ UI Components
- βοΈ Business Logic
- ποΈ Database/Data
- π Documentation
- β Tests
π Deployment Status
- Can it be deployed? (yes/no)
- Build status (passing/failing)
- Any blockers?
β Quality Checks
- Tests: Passing/Failing (count)
- Type errors: None/Count
- Lint issues: None/Count
- Accessibility: β /β οΈ
π Complexity Summary
- Files changed: [count]
- Lines added: [count]
- Lines removed: [count]
- Complexity rating: Simple/Medium/Complex
π‘ What This Means
Summarize in 2-3 sentences:
- Where we are in the feature
- What's working
- What's left to do (if anything)
π― Next Steps
- Immediate actions needed
- Ready for review? (yes/no)
- Ready to deploy? (yes/no)
Note: Use simple language. Focus on product impact, not technical details.