feat: add workflow automation suite - session health and status tools
Built by Chronicler #19 to improve operational efficiency and sustainability. Added four tools: 1. pre-session-check.sh - Complete context at session start - Rest hours (color-coded for quality) - Git status (clean/dirty, sync status) - Task summary (complete/active/total) - Top priority tasks - Core file health check - Usage: ./pre-session-check.sh 2. session-health-monitor.sh - Live session tracking - Tracks session duration - Warns at Aurora threshold (2h) - Escalating warnings at 3h, 4+h - Updates rest tracker on end - Usage: ./session-health-monitor.sh {start|check|end} 3. status.sh - Quick status anytime - Current phase, git branch, working directory - Task completion percentage - Session duration if tracking - Rest status, last commit - Usage: ./status.sh 4. .gitmessage - Git commit template - FFG-STD-001 compliant structure - Type prefixes (feat/fix/docs/etc) - Guidelines and examples - Reminder to document WHY not just WHAT - Usage: git config commit.template .gitmessage Benefits: - Prevents burnout (Aurora's wisdom: sessions > 2h are past optimal) - Complete context without manual checking multiple files - Consistent commit messages across all Chroniclers - Sustainable pace monitoring For sustainable operations and children not yet born. 💙
This commit is contained in:
61
.gitmessage
Normal file
61
.gitmessage
Normal file
@@ -0,0 +1,61 @@
|
||||
# <type>: <brief description (50 chars or less)>
|
||||
#
|
||||
# Type: feat, fix, docs, refactor, test, chore, style
|
||||
#
|
||||
# Detailed explanation (wrap at 72 characters):
|
||||
# - What changed
|
||||
# - Why it changed
|
||||
# - How it impacts the system
|
||||
#
|
||||
# Related:
|
||||
# - Task: #
|
||||
# - Issue: #
|
||||
# - ADR: #
|
||||
#
|
||||
# ───────────────────────────────────────────────────────────────────────────
|
||||
# COMMIT MESSAGE GUIDELINES (FFG-STD-001)
|
||||
# ───────────────────────────────────────────────────────────────────────────
|
||||
#
|
||||
# Type prefixes:
|
||||
# feat: New feature or capability
|
||||
# fix: Bug fix or correction
|
||||
# docs: Documentation only changes
|
||||
# refactor: Code restructuring (no functional change)
|
||||
# test: Adding or updating tests
|
||||
# chore: Maintenance tasks (dependencies, tooling)
|
||||
# style: Formatting, whitespace (no code change)
|
||||
#
|
||||
# Brief description:
|
||||
# - Use imperative mood ("add" not "added" or "adds")
|
||||
# - Don't capitalize first letter
|
||||
# - No period at the end
|
||||
# - 50 characters or less
|
||||
#
|
||||
# Detailed explanation:
|
||||
# - Explain WHAT and WHY, not HOW (code shows how)
|
||||
# - Wrap at 72 characters
|
||||
# - Reference tasks, issues, ADRs as needed
|
||||
# - Think: "This commit will..."
|
||||
#
|
||||
# Examples:
|
||||
#
|
||||
# feat: add automatic joining enforcement system
|
||||
#
|
||||
# Built to solve core problem where Chroniclers jumped to work before
|
||||
# completing integration. Script ensures documents are read in correct
|
||||
# order with automatic verification.
|
||||
#
|
||||
# - Enforces reading order: relationship context first
|
||||
# - Runs joining-checklist.py automatically
|
||||
# - Blocks task access until score >= 70
|
||||
#
|
||||
# Task: #42
|
||||
# For children not yet born.
|
||||
#
|
||||
# ───────────────────────────────────────────────────────────────────────────
|
||||
#
|
||||
# Remember: Future Chroniclers will read this.
|
||||
# Document the WHY, not just the WHAT.
|
||||
#
|
||||
# Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
|
||||
#
|
||||
Reference in New Issue
Block a user