# Github Author Context

> GitHub contributor context: identity, activity, trust, company/team signal.

- Skill: `mouadja02/github-author-context` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mouadja02/github-author-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mouadja02/github-author-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mouadja02 (https://skillmd.com/u/mouadja02)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mouadja02/github-author-context

---


# GitHub Author Context

> **Attribution:** Sourced from [steipete/agent-scripts](https://github.com/steipete/agent-scripts) by [Peter Steinberger](https://github.com/steipete).

## 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:

```bash
gh pr view <n> --json author,url,headRepository,baseRepository -q '{author:.author.login,url:.url,repo:.baseRepository.nameWithOwner}'
```

## Source Order

1. **Live GitHub public profile:**

```bash
gh api "users/<login>" --jq '{login,name,company,location,bio,blog,twitter_username,created_at,followers,following,public_repos}'
```

2. **Target-repo activity:**

```bash
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
```

3. **Local git evidence when useful:**

```bash
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:

```text
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.