mouadja02 GitHub Author Context
Attribution: Sourced from steipete/agent-scripts by Peter Steinberger.
When to Use
- Building contributor profiles for PR review context
- Assessing trust signals (activity, company, commit history) of a PR author
- Triaging PRs from unknown contributors
Build a compact maintainer-facing profile for a PR author or GitHub user. Use this by default during PR review to understand contributor identity, trust level, and activity history.
Inputs
Prefer a GitHub login. From a PR:
gh pr view <n> --json author,url,headRepository,baseRepository -q '{author:.author.login,url:.url,repo:.baseRepository.nameWithOwner}'
Source Order
- Live GitHub public profile:
gh api "users/<login>" --jq '{login,name,company,location,bio,blog,twitter_username,created_at,followers,following,public_repos}'
- Target-repo activity:
gh search prs --repo <owner/repo> --author <login> --state merged --limit 20 --json number,title,mergedAt,url
gh search prs --repo <owner/repo> --author <login> --state open --limit 20 --json number,title,updatedAt,url
gh search issues --repo <owner/repo> --author <login> --state open --limit 20 --json number,title,updatedAt,url
gh api "repos/<owner>/<repo>/collaborators/<login>/permission" --jq '{permission,user:.user.login}' 2>/dev/null || true
- Local git evidence when useful:
git log --all --author="<login>" --since="90 days ago" --oneline --decorate --no-merges | head -40
git shortlog -sne --all | rg -i "<login>|<name>|<email>"
Output
Keep it short. Add this block near the top of a PR review:
Author context: @login
- Who: <name/company/location/role, confidence>
- Activity: <merged/open PRs, issues, reviews/commits if known>
- Signal: <maintainer/candidate/drive-by/vendor/security/unknown>
- Risk: <review-load, broad PRs, low history, company-governance, none obvious>
Do not quote private phone/email/contact details. Separate employer from company-directed work; almost everyone has an employer.
Contributor Notes
After a merge/rejection/close/review, add a note only if it creates future review value: first good merge, unusually strong work, repeated quality problems, slop, no-repro churn, exceptional responsiveness, lack of follow-through, or identity confirmation.
Keep notes terse, factual, dated, and linked. Do not record ordinary noise.