skillmake
← marketplace
engineerstoolsha:f830264b16615c24manual

github-author-context

Use when working with gitHub contributor context: identity, activity, trust, company/team signal from steipete/agent-scripts.

Install confidence
curl --create-dirs -fsSL https://skillmake.xyz/i/github-author-context -o ~/.claude/skills/github-author-context/SKILL.md
Pinned content
sha:f830264b16615c24
Generated with
manual
Source
github.com

The file served at /api/marketplace/github-author-context-f830264b/raw matches this hash. Inspect before install, then copy the command.

4,816 chars · ~1,204 tokens
---
name: github-author-context
description: "Use when working with gitHub contributor context: identity, activity, trust, company/team signal from steipete/agent-scripts."
source: https://github.com/steipete/agent-scripts/tree/main/skills/github-author-context
generated: 2026-05-27T20:55:41.116Z
category: tool
audience: engineers
---

## When to use

- Using the github-author-context skill's upstream workflow, guardrails, and local-tool assumptions.
- Auditing commands or operational steps before changing github author context behavior.
- Needing a compact agent reference for gitHub contributor context: identity, activity, trust, company/team signal.

## Key concepts

### Inputs

Prefer a GitHub login. From a PR: Skip the profile pass for steipete unless the user explicitly asks.

### Source Order

1. OpenClaw contributor notes: If a contributor file matches in ~/Projects/maintainers/contributors/people, read only: Identity Signals Context Evidence Notes Fallback only when the new contributor file is missing and old maintainer context might help: If an old person file matches, read only the relevant sections: Verdict Identity Company Affiliation Metrics Discord Communication Evidence Risks / Concerns / Recommendation when present 2. Live GitHub public profile: 3. Target-repo activity...

### Output

Keep it short. Add this block near the top of a PR review: Do not quote private phone/email/contact details unless Peter asks. Separate employer from company-directed OpenClaw 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. Use the maintainer repo helper so Markdown stays consistent: Keep notes terse, factual, dated, and linked. Do not record ordinary noise.

## API reference

```
npx skills add steipete/agent-scripts --skill github-author-context
```

Install the github-author-context skill from steipete/agent-scripts.

```
npx skills add steipete/agent-scripts --skill github-author-context
```

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

Command or snippet documented by the upstream github-author-context skill.

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

```
~/Projects/maintainers/scripts/clawtributors find github <login>.
```

Command or snippet documented by the upstream github-author-context skill.

```
~/Projects/maintainers/scripts/clawtributors find github <login>
```

```
rg -n -i "<login>|<name>|<discord>" ~/Projects/openclaw-maintainers/people ~/Projects/openclaw-maintainers/data.
```

Command or snippet documented by the upstream github-author-context skill.

```
rg -n -i "<login>|<name>|<discord>" ~/Projects/openclaw-maintainers/people ~/Projects/openclaw-maintainers/data
```

```
gh api "users/<login>" --jq '{login,name,company,location,bio,blog,twitterusername,createdat,followers,following...
```

Command or snippet documented by the upstream github-author-context skill.

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

```
gh search prs --repo <owner/repo> --author <login> --state merged --limit 20 --json number,title,mergedAt,url.
```

Command or snippet documented by the upstream github-author-context skill.

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

```
git log --all --author="<login>" --since="90 days ago" --oneline --decorate --no-merges | head -40.
```

Command or snippet documented by the upstream github-author-context skill.

```
git log --all --author="<login>" --since="90 days ago" --oneline --decorate --no-merges | head -40
git shortlog -sne --all | rg -i "<login>|<name>|<email>"
```

## Gotchas

- Prefer a GitHub login. From a PR:.
- Do not quote private phone/email/contact details unless Peter asks. Separate employer from company-directed OpenClaw work; almost everyone has an employer.

---
Generated by SkillMake from https://github.com/steipete/agent-scripts/tree/main/skills/github-author-context on 2026-05-27T20:55:41.116Z.
Verify against source before relying on details.

File: ~/.claude/skills/github-author-context/SKILL.md