Dev Workflow

GitHub (via gh CLI):

# Open PRs
gh pr list --state open --json number,title,author,createdAt,reviewDecision,statusCheckRollup
# Recent merged PRs
gh pr list --state merged --json number,title,mergedAt --limit 10
# Open issues assigned to user
gh issue list --assignee @me --state open --json number,title,labels
# CI status on current branch
gh run list --limit 5 --json status,conclusion,name,createdAt

Git (local state):

# Recent commits
git log --oneline -20 --format="%h %s (%an, %ar)"
# Branch status
git branch -vv
# Uncommitted changes
git status --short

Build/Tests (project-specific):

# Run build check
npm run build 2>&1 | tail -20  # or equivalent
# Run test suite
npm test 2>&1 | tail -30  # or equivalent

Error Tracking (if Sentry MCP available):

• Recent unresolved errors
• Error frequency trends
• Errors correlated with recent deploys

2. Cross-Reference and Analyze: Connect data across sources

   • Which commits are in which PRs?
   • Which CI failures correspond to which commits?
   • Which errors appeared after which deployments?
   • Which PRs are blocked by failing CI checks?
   • Which issues are addressed by open PRs?

3. Generate Report: Format developer status report

   # Developer Report - YYYY-MM-DD
   
   ## Critical (Action Required)
   - CI FAILING: main branch build broken since commit abc123 (2h ago)
   - ERROR SPIKE: 500 errors up 300% in auth service since deploy v1.2.3
   
   ## PRs Requiring Attention
   | PR | Title | Author | Status | CI | Age |
   |----|-------|--------|--------|-----|-----|
   | #42 | Fix auth timeout | @alice | Approved | Passing | 2d |
   | #38 | Refactor DB layer | @bob | Changes requested | Failing | 5d |
   
   ## Recent Activity
   - 5 commits merged today
   - 2 new issues opened
   - 1 deployment completed (v1.2.3)
   
   ## Code Health
   - Build: PASSING
   - Tests: 142 passed, 0 failed
   - Coverage: 78.5%
   

4. Store for Trend Tracking: Log report data in memory

   sc_memory_store(
     content="Dev report YYYY-MM-DD: build=pass, tests=142/142, open_prs=5, errors=3",
     category="dev-report",
     confidence=1.0
   )
   

   • Enables: "show me build health over the past month"
   • Enables: "when did test failures start increasing?"

5. Alert on Critical Items: Send urgent items to Telegram

   sc_send_message(
     message="ALERT: CI broken on main. Commit abc123 by @alice. Error: TypeScript compilation failed.",
     priority="high"
   )
   

   • Only alert for: build failures on main, error rate spikes, security vulnerabilities
   • Never alert for: informational updates, non-blocking PR status

# Morning Brief - {{DATE}}

## Overnight Summary
- Commits merged: {{N}}
- PRs opened: {{N}} | merged: {{N}} | closed: {{N}}
- CI status: {{PASSING/FAILING}} (main branch)
- New errors: {{N}} ({{SEVERITY}})

## Action Items
1. {{CRITICAL_ITEM}} - {{CONTEXT}}
2. {{REVIEW_NEEDED}} - PR #{{N}} by {{AUTHOR}}
3. {{FOLLOW_UP}} - {{CONTEXT}}

## Your Open PRs
| PR | Status | CI | Last Activity |
|----|--------|-----|--------------|
{{PR_TABLE}}

## Team Activity
{{ACTIVITY_SUMMARY}}

PR Review Checklist

When reviewing PRs via this workflow:

• CI checks passing
• No merge conflicts
• Code coverage maintained or improved
• No security warnings in dependencies
• Related issues linked
• Description explains the "why" not just the "what"

CI Failure Triage Guide

CI Failure
├── Build failure
│   ├── TypeScript error → Check recent type changes
│   ├── Import error → Check for missing dependencies
│   └── Compilation error → Check for syntax issues
├── Test failure
│   ├── Assertion error → Check expected vs actual values
│   ├── Timeout → Check for async issues or infinite loops
│   └── Setup error → Check test fixtures and mocks
└── Lint/Format failure
    ├── ESLint → Run auto-fix: npx eslint --fix
    └── Prettier → Run auto-fix: npx prettier --write

Custom Report Templates

Users can customize reports by modifying templates in: ~/superclaw/config/report-templates/

Available template variables:

• {{DATE}}, {{TIME}} -- Current date/time
• {{BRANCH}} -- Current git branch
• {{PR_COUNT}}, {{ISSUE_COUNT}} -- Counts
• {{CI_STATUS}} -- Build status
• {{ERROR_COUNT}} -- Error tracker count

Team-Wide Dashboards

For multi-developer projects:

# All team members' PR status
gh pr list --state open --json number,title,author,reviewDecision

# Contribution stats
git shortlog -sn --since="1 week ago"

# File hotspots (most changed files)
git log --since="1 week ago" --name-only --format="" | sort | uniq -c | sort -rn | head -20

Integration with Automation Pipeline

Schedule daily reports via SuperClaw's cron system:

sc_cron_add(
  name="daily-dev-report",
  schedule="0 9 * * 1-5",  # 9 AM weekdays
  command="superclaw dev-workflow morning-brief"
)

Deployment Tracking

Track deployment history:

sc_memory_add_entity(
  name="deploy-v1.2.3",
  type="deployment",
  properties={version: "1.2.3", timestamp: "...", commit: "abc123", environment: "production"}
)
sc_memory_add_relation(from="deploy-v1.2.3", to="pr-42", type="includes")
sc_memory_add_relation(from="deploy-v1.2.3", to="pr-38", type="includes")

Query: "what PRs were in the last production deploy?"

sc_memory_graph_query(query="deployment production latest includes")

Troubleshooting

gh CLI not found?

• Install: brew install gh (macOS) or see https://cli.github.com/
• Authenticate: gh auth login

Build command unknown?

• Check package.json for scripts (npm/yarn/pnpm)
• Check Makefile for targets
• Check for CI config files (.github/workflows/, .gitlab-ci.yml)

Rate limited by GitHub API?

• gh CLI handles authentication automatically
• For heavy usage, consider using --limit flags
• Cache responses in memory for repeated queries within the same session