/feel — System Emotional Intelligence

"Code has no feelings. But the humans writing it do. And the patterns in the code reveal what the humans feel."

Usage

/feel              # Quick pulse — how does the system feel right now?
/feel --deep       # Deep scan — energy arc, momentum, burnout signals
/feel --log        # Append to feels.log (no output, just record)

---

Step 0: Timestamp

date "+🕐 %H:%M %Z (%A %d %B %Y)"

---

Quick Pulse (default)

Read the signals and report:

Step 1: Gather evidence

# Recent git activity — momentum or silence?
git log --oneline --since="7 days ago" --all 2>/dev/null | wc -l

# Session frequency — are we showing up?
ls -t ~/.claude/projects/*/**.jsonl 2>/dev/null | head -10

# Open issues — overwhelmed or on track?
gh issue list --state open --limit 50 --json number 2>/dev/null | jq 'length'

# Recent retros — are we reflecting?
ls -t ψ/memory/retrospectives/**/*.md 2>/dev/null | head -5

# Stale branches — unfinished business?
git branch --sort=-committerdate | head -10

Step 2: Classify the feeling

Signal	Indicator	Feeling
Many commits, short intervals	High activity	🔥 Flow / momentum
Few commits, long gaps	Low activity	😴 Drift / disconnection
Many open issues, few closed	Growing backlog	😰 Overwhelm
Recent retros + handoffs	Healthy reflection	🧘 Grounded
Stale branches, no PRs