Behavioural Process Intelligence · Public Mirror
Prettier
What we read from 300 public GitHub events across the last 3 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Prettier · May 9, 2026
fisker is carrying 96% of the human writing work.
16 PRs merged with no independent review. Spans 2 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
prettier/prettier#18893·prettier/prettier#19130·prettier/prettier#19129·prettier/prettier#19128·prettier/plugin-xml#1000
fisker is carrying 96% of the human writing work. 22 of 23 commit + PR-open + PR-merge events concentrated on a single human contributor. Bus-factor risk visible from the public feed.
fisker authored 19/19 commits in prettier/prettier. 100% concentration in this window. If fisker stops, prettier/prettier stalls.
72% of writing this window was automated. renovate[bot] accounts for 47 of 60 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
2 PRs merged between 22:00 and 06:00 UTC. Spans 1 repo. Either an always-on global org or a deploy-late-night habit.
prettier/prettier carried 71% of activity. 214 of 300 events in the last 3 weeks. Next: prettier/prettier-vscode (41).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- prettier/prettier214 events · 29 commits · 14/17 PRs
- prettier/prettier-vscode41 events · 0 commits · 0/3 PRs
- prettier/plugin-xml19 events · 2 commits · 2/2 PRs
- prettier/angular-estree-parser8 events · 0 commits · 0/1 PRs
- prettier/prettier-eslint5 events · 5 commits · 0/0 PRs
- prettier/pretty-quick5 events · 3 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @fisker38 events · 42% share
- @aybekjo19722 events · 2% share
- @bangseongbeom2 events · 2% share
- @natanthekiller221 event · 1% share
- @WolffM1 event · 1% share
- @paulofduarte1 event · 1% share
FIG 5 · Rituals we can't see from GitHub alone
Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:
Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream
This is what we'd see for your team.
Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.
Book a demo →FIG 6 · Embed in your README
Paste this in your README. The badge updates daily and links back to this Mirror.
[](https://www.assemblr.net/mirror/prettier)