Team_Hero

Coming Soon

Automated weekly status reports for engineering managers.
Free, open source, and almost ready.

Star on GitHub
Free & Open Source CLI for Engineering Managers

Automate your weekly status report.
Five minutes and 2¢.

Team Hero connects to your GitHub and Asana, reads your meeting notes, reconciles the conflicts, and writes the report for you.

curl -fsSL https://github.com/asabaylus/teamhero.scripts/releases/latest/download/install.sh | bash
View on GitHub
★ — stars  ·  MIT License
Integrates with
GitHub Asana Meeting Transcripts Jira soon Linear soon

// The Problem

You know this Friday. It's 6 PM. You have five tabs open: GitHub, Asana, last week's meeting transcript, the Google Doc you copy from every time, and a Slack thread where someone mentioned a blocker that definitely isn't in the ticket system. You're going to spend the next several hours stitching all of this together into something defensible before you can stop working.

The worst part? It's not that you're slow. It's that the data lives everywhere and nothing agrees. A PR got merged but the ticket is still open. The sprint velocity looks fine until you account for the two engineers who were heads-down on an incident. The meeting transcript says one thing; the Asana task says another. Someone has to reconcile all of it. That someone is you. Every single week.

"Save yourself hours every week. Because writing status reports is soul sucking work."

There's a better way. And it's OpenSource.

// How It Works

Install. Setup. Report.
That's the whole thing.

STEP 01 — INSTALL
One line to install

Homebrew, curl, or APT — pick your platform. Works on macOS, Linux, and Windows via WSL. Also ships as a Claude Code plugin.

STEP 02 — SETUP
Connect your accounts

Run the guided setup wizard. Add your GitHub token and OpenAI key. Optionally connect Asana and Google Drive for meeting transcripts. Takes about two minutes.

STEP 03 — REPORT
Generate your report

Pick your org, repos, team members, date range, and sections from the interactive TUI. Team Hero pulls, reconciles, and writes. ~5 minutes. ~2¢.

$ teamhero report
STEP 04 — REVIEW & SEND
Check the discrepancies

Team Hero flags where your data sources disagree. Review the discrepancy log, amend what you want, and send it. Next week, just re-run — your settings are saved.

// What You Get

A report your boss
can actually verify.

teamhero-report-acme-eng-2026-03-14.md
$ teamhero report --headless --foreground
✔ Organization ready: Acme Engineering (acme-eng) — 0:00
✔ Repositories queued: 28 — 0:01
✔ Members queued: 6 — 0:01
→ Calculating repository metrics (28 repos)...
→ Fetching Asana tasks for "Platform Q1"...
→ Ingesting 3 meeting transcripts...
→ Reconciling sources and generating report...
→ Done in 4m 12s (~$0.02)

## This Week's Visible Wins & Delivered Outcomes

Auth Service
* Token validation refactor shipped; 40% latency
reduction confirmed in load tests (completed).
* Session storage migration blocked by compliance
review; legal sign-off expected Monday (blocked).

Payments
* Stripe webhook retry logic merged; resolves
dropped events under rate limiting (completed).

## Weekly Engineering Summary (2026-03-08 – 2026-03-14)
Processed 34 PRs across 28 repositories,
with contributions from 6 engineers, 19 merged.

## Discrepancy Report
1. PR #412 merged Wed — Asana task "Payments refactor"
still shows In Progress. Recommend: close ticket.
Contributor: Sarah Chen | Confidence: 90%

✓ Report saved: teamhero-report-acme-eng-2026-03-14.md
📊 Hard numbers, real sources
PRs, commits, task counts, velocity — pulled directly from GitHub and Asana, not guessed. Every number in the report is defensible.
⚠️ Discrepancy log
Team Hero catches conflicts between your data sources before your boss does. The ticket that says one thing and the PR that says another — flagged, every time.
🎛️ Configurable sections
Generate only what your executive actually reads. Skip what's irrelevant. Adjust scope per team, per project, per week.
💸 Your API key. Your cost.
No subscription. No premium tier. Bring your own AI API key. Team Hero uses it for inference and gets out of the way.
≈ $0.02 per report

// The Obvious Question

Why not just ask an AI?

Fair question. Yes, any AI — ChatGPT, Claude, Gemini — can write a status report. Give it a template and some bullet points and you'll get a perfectly decent document back. Nobody's disputing that.

Here's the problem: the writing isn't where the 6 hours goes. The 6 hours goes to gathering — opening GitHub, opening Asana, cross-referencing a meeting transcript from Tuesday that contradicts what the ticket says, figuring out why the sprint velocity looks off, tracking down the PR that got merged but never closed. That part is manual. That part is brutal. And a general-purpose AI does exactly none of it.

Team Hero does that part. It connects to your actual sources, pulls the actual data, reconciles the actual conflicts, and then — yes — uses an AI model to write the prose. The writing is fast. It was always fast. The work is the gathering. That's what Team Hero is for.

"Any AI can write the report.
Team Hero actually knows what happened."

// Built to Grow

Integrations today.
More on the way.

Integration Status Details
GitHub Live PRs, commits, reviews, contributors
Asana Live Projects, tasks, priorities, blockers
Meeting Transcripts Live Static files ingested via config
Jira Coming Soon On the roadmap
Linear Coming Soon On the roadmap
Built for the terminal.
Ready for your pipeline.

Team Hero's CLI is fully non-interactive — every action available in the terminal works headlessly. No prompts, no GUI, no surprises. Drop it into GitHub Actions, run it from Claude Code, or wire it into your own automation without modification.

GitHub Actions Claude Code CI/CD pipelines cron jobs headless

Install Team Hero

Choose your platform. One command to get started.

Homebrew (recommended)
brew install asabaylus/teamhero/teamhero
curl
curl -fsSL https://github.com/asabaylus/teamhero.scripts/releases/latest/download/install.sh | bash
Then run setup
teamhero setup && teamhero doctor
APT (Debian / Ubuntu)
curl -fsSL https://apt.teamhero.dev/teamhero.gpg | sudo gpg --dearmor -o /usr/share/keyrings/teamhero.gpg echo "deb [signed-by=/usr/share/keyrings/teamhero.gpg] https://apt.teamhero.dev stable main" | sudo tee /etc/apt/sources.list.d/teamhero.list sudo apt-get update && sudo apt-get install teamhero
Homebrew
brew install asabaylus/teamhero/teamhero
curl
curl -fsSL https://github.com/asabaylus/teamhero.scripts/releases/latest/download/install.sh | bash
Then run setup
teamhero setup && teamhero doctor
Windows (via WSL)

Team Hero runs natively on WSL. Open your WSL terminal and use any Linux install method.

curl -fsSL https://github.com/asabaylus/teamhero.scripts/releases/latest/download/install.sh | bash
Then run setup
teamhero setup && teamhero doctor
Claude Code Plugin

Use Team Hero directly from Claude Code without a separate install. Just tell Claude to generate your report.

claude plugin marketplace add asabaylus/teamhero.scripts claude plugin install teamhero-scripts@teamhero
Then just ask
Generate a Team Hero report for my org for the last two weeks
teamhero-report-acme-eng-2026-03-14.md Example Report

This Week's Visible Wins & Delivered Outcomes

Auth Service

  • Token validation refactor shipped Thursday; load tests confirm 40% latency reduction (completed).
  • Session storage migration blocked by compliance review; legal sign-off expected Monday (blocked).
  • Rate-limiter tuning deployed to staging; production rollout pending QA sign-off (in progress).

Payments

  • Stripe webhook retry logic merged; resolves dropped events under rate limiting (completed).
  • Subscription billing audit script delivered; identified 12 mismatched renewal dates (completed).
  • PCI scope reduction documentation submitted to auditor (in progress).

Infrastructure

  • Kubernetes node pool migration completed; all workloads running on ARM instances (completed).
  • Staging environment instability root-caused to memory limits; fix deployed (completed).

Onboarding

  • Email verification flow redesigned; conversion rate data expected next week (in progress).
  • SSO integration with Okta scoped; estimate is 3 sprints (scheduled).

Progress on Quarterly Roadmap

Initiative / Epic Next Milestone & Date Status Key Notes
Auth v2 — Zero-trust session management Mar 21 — Production rollout On Track Token refactor shipped; session storage blocked on legal review. Rate-limiter in staging.
Payments — PCI scope reduction Apr 5 — Audit submission On Track Webhook retry shipped. Billing audit complete. PCI docs submitted.
Platform — ARM migration Mar 14 — Complete Done All workloads migrated. ~18% compute cost reduction observed.
Growth — Onboarding redesign Apr 15 — A/B test launch At Risk Email verification redesigned but conversion data pending. SSO scoped at 3 sprints.

Weekly Engineering Summary (2026-03-08 – 2026-03-14)

Processed 34 PRs across 28 repositories, with contributions from 6 engineers, 19 merged during the window.

At-a-Glance Summary

Developer Commits PRs Opened PRs Merged Lines Added Lines Deleted Reviews
Sarah Chen 47 6 5 3,218 891 4
Marcus Rivera 31 4 4 1,842 2,106 6
Priya Patel 28 5 4 4,521 312 3
Jake Morrison 19 3 3 967 1,445 2
Lin Wei 22 4 2 2,890 154 5
Alex Okafor 8 2 1 423 67 0
Note: This table provides a quick view of activity across the team. Reviews are counted as approved, changes requested, or commented.

Individual Updates

Sarah Chen (@sarahchen)

Sarah led the auth token validation refactor, replacing the legacy JWT verification chain with a streamlined middleware that eliminates redundant database lookups on every request. Load tests show a 40% reduction in p95 latency for authenticated endpoints. She also completed the Stripe webhook retry implementation, adding exponential backoff and idempotency checks that resolve the dropped-event issue reported by the payments team last sprint. Both changes are merged and running in production.

Marcus Rivera (@marcusrivera)

Marcus completed the Kubernetes ARM migration, moving all production workloads from x86 to Graviton instances and updating the Helm charts and CI pipelines accordingly. Early metrics show an ~18% reduction in compute costs. He also root-caused the staging environment instability to undersized memory limits on the API gateway pods and deployed a fix. Both the migration and the staging fix are live.

Priya Patel (@priyapatel)

Priya built the subscription billing audit script that cross-references Stripe subscription records against the internal billing database, identifying 12 accounts with mismatched renewal dates. She also drafted the PCI scope reduction documentation and submitted it to the external auditor. The email verification flow redesign is in progress with the new templates deployed to staging, though conversion data won't be available until next week's A/B test begins.

Jake Morrison (@jakemorrison)

Jake delivered the rate-limiter tuning for the auth service, adjusting per-endpoint thresholds based on production traffic patterns from the last 90 days. The changes are deployed to staging and awaiting QA sign-off before production rollout. He also reviewed and approved three PRs across the auth and payments services.

Lin Wei (@linwei)

Lin scoped the Okta SSO integration, producing a technical design document and estimating the work at three sprints. She also advanced the onboarding flow redesign by implementing the new email verification UI components and writing integration tests for the verification endpoint. The SSO work is scheduled to begin next sprint pending product prioritization.

Alex Okafor (@alexokafor)

No notable shipped outcomes were delivered by Alex Okafor during Mar 8, 2026 – Mar 14, 2026.

Discrepancy Report

Period: Mar 8, 2026 – Mar 14, 2026  |  Generated: Mar 14, 2026, 5:23 PM

# Issue Contributor Confidence
1 PR #412 merged Wednesday — Asana task "Stripe webhook retry" still shows In Progress. Sarah Chen 90%
2 Report claims ~18% compute cost reduction from ARM migration, but no cost dashboard or billing data provided. Marcus Rivera 85%
3 Report states "12 mismatched renewal dates" identified, but billing audit script PR does not include validation tests. Priya Patel 80%
4 Report attributes rate-limiter tuning to production traffic analysis but no traffic data or methodology referenced. Jake Morrison 75%

1. PR #412 merged Wednesday — Asana task still shows In Progress.

Contributor: Sarah Chen (@sarahchen)  |  Confidence: 90%

GitHub PR #412 ("feat: Stripe webhook retry with exponential backoff") was merged on Wednesday, Mar 12. However, the corresponding Asana task "Implement webhook retry logic" remains in the "In Progress" column of the Payments sprint board. The task was not moved to "Done" after the PR merge.

Evidence:

  • GitHub PR #412 — MERGED, Mar 12
  • Asana task "Implement webhook retry logic" — Status: In Progress

Action: Close the Asana task or update its status to reflect the merged PR.

2. Report claims ~18% compute cost reduction but no billing data provided.

Contributor: Marcus Rivera (@marcusrivera)  |  Confidence: 85%

The individual summary states the ARM migration yielded "~18% reduction in compute costs." The merged PRs (Helm chart updates, CI pipeline changes) confirm the migration was completed, but no cost dashboard screenshot, billing comparison, or AWS Cost Explorer data was provided. The claim is plausible given known Graviton pricing but not verifiable from the provided evidence.

Evidence:

  • GitHub PRs #398, #401, #405 — MERGED (Helm charts, CI pipelines)
  • No cost data, billing reports, or dashboard references provided

Action: Attach AWS billing comparison or Cost Explorer data to support the claimed reduction, or soften language to "expected ~18% reduction based on Graviton pricing."

3. Billing audit script PR lacks validation tests.

Contributor: Priya Patel (@priyapatel)  |  Confidence: 80%

The report states the billing audit script "identified 12 accounts with mismatched renewal dates." PR #409 contains the script but no unit or integration tests validating the mismatch-detection logic. Without tests, the accuracy of the "12 accounts" figure cannot be independently verified.

Evidence:

  • GitHub PR #409 — MERGED, contains audit script
  • No test files in PR diff

Action: Add tests for the audit script's matching logic, or provide the raw output log that shows the 12 identified accounts.

4. Rate-limiter tuning claims based on traffic analysis without supporting data.

Contributor: Jake Morrison (@jakemorrison)  |  Confidence: 75%

The report states rate-limiter thresholds were "adjusted based on production traffic patterns from the last 90 days." PR #415 updates the rate-limit configuration values but includes no traffic analysis, methodology notes, or references to monitoring dashboards that informed the new thresholds.

Evidence:

  • GitHub PR #415 — OPEN (staging), config changes only
  • No traffic data, Grafana links, or analysis documents referenced

Action: Reference the traffic analysis or monitoring dashboard used to determine the new thresholds, or note that values were set based on engineering judgment rather than empirical data.