Skip to content
Shell
1.1 KB
Raw Blame

/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.