Skip to content
BSWEN
Blog

How /last30days's GitHub Person-Mode Finds What Developers Are Actually Shipping

Cowrie
Cowrie
Dev @ Bswen

Purpose

When I search for a developer on GitHub, the default search matches keywords across all of GitHub — every issue, every comment, every PR body that mentions the name. Searching “steipete” returns hundreds of results where someone mentioned the name in a thread, but tells me nothing about what steipete actually shipped.

/last30days’s GitHub person-mode solves this by switching from keyword search to author-scoped queries when the topic is a person.

The Difference

Here’s what keyword search returns versus person-mode:

Keyword search vs person-mode
Standard keyword search for "steipete":
  - Issue #42: "Hey @steipete, can you review this?"
  - PR #128: "Thanks steipete for the suggestion"
  - Comment: "steipete mentioned this in another thread"
  → Noise. Mentions of the name, not what they did.


Person-mode (--github-user=steipete):
  - 22 PRs authored in the last 30 days
  - 3 active repos maintained
  - 85% merge rate across all PRs
  - 2 new releases published this month
  → Signal. What they actually shipped.

How It Works

When the engine detects a person as the topic (either by the --github-user flag or through automatic resolution in Step 0.5b), it switches search mode:

Author-scoped queries: Instead of searching for the name anywhere in GitHub, it scopes to user:{handle}. This means it only finds results where the person is the author — not just a mention.

What it fetches:

  • PRs authored by the user with merge status and review counts
  • Owned projects with README summaries, star counts, and latest releases
  • Release notes for what shipped this month
  • Top feature requests and issue discussions in their repos

Integration into the brief: The GitHub data doesn’t stand alone. The synthesizer weaves it into the narrative alongside X posts, Reddit threads, and YouTube transcripts.

Person-mode query
/last30days Peter Steinberger --github-user=steipete

The result includes:

What the engine returns
GitHub: 22 PRs merged, 3 repos active, 85% merge rate
X: @steipete active on Codex discussions
Reddit: r/ClaudeCode discussing steipete's work

Why This Matters

For developer research — recruiting, competitor analysis, due diligence — knowing what someone shipped in the last 30 days is far more valuable than keyword matches. “22 PRs at 85% merge rate” tells a story that LinkedIn summaries cannot. Combined with X posts and Reddit discussions, you get a 360-degree view of what any developer is doing right now.

Summary

In this post, I explained how /last30days’s GitHub person-mode transforms developer research from keyword noise to a focused activity report. The key point is that when you want to know what a developer is actually shipping, person-mode gives you PRs, repos, and releases — not random mentions.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: