Skip to content

notque/vexjoy-agent / skills/process/pr-workflow

pr-workflow

Flagged

Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining. Use when user wants to commit changes, get a second-opinion code review from Codex, push changes, create a PR, check PR status, fix review comments, clean up branches after merge, or mine tribal knowledge from PR reviews. Use for "commit my changes", "codex review", "push my changes", "create a PR", "pr status", "fix PR comments", "clean up branches", "mine PRs", or "address feedback".

references/reviewer-usernames.md

View on GitHub
# Known GitHub Reviewer Usernames

## Overview

When mining PR review patterns, you need to know the correct GitHub usernames of reviewers. This file documents how to discover and verify reviewer usernames.

## Common Reviewers

### Special Accounts
- **github-advanced-security** - Dependabot and security scanning
- **dependabot** - Automated dependency updates
- **codecov** - Code coverage bot

## Usage Patterns

### Mining Senior Reviewer Patterns
For senior reviewers, use `--all-comments` flag:
```bash
--reviewer username --all-comments
```

**Why**: Senior reviewers often use questions and explanations instead of direct imperative language:
- "Maybe use errors.Is() here?" (question form)
- "I would prefer X because Y" (suggestion with rationale)
- "Consider using Z for performance" (recommendation)

### Mining Team Standards
For broad team standards, omit `--reviewer` to capture all perspectives:
```bash
# No --reviewer flag = all reviewers
./venv/bin/python3 scripts/miner.py your-org/your-repo mined_data/output.json
```

## Verifying Reviewer Usernames

### Method 1: Mine Without Filter
```bash
./venv/bin/python3 scripts/miner.py \
  your-org/your-repo \
  mined_data/check.json \
  --limit 50 --summary
```

Check the summary output for top reviewers list.

### Method 2: GitHub API Directly
```bash
curl -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/your-org/your-repo/pulls/comments | \
  jq -r '.[].user.login' | sort | uniq -c | sort -rn
```

## Common Username Mistakes

### Capitalization
- GitHub usernames are case-insensitive for API queries
- But display names may differ from login names
- Always verify the exact login format

## Updating This List

When you discover new reviewer usernames:
1. Add to your `.local/` overlay (not this file)
2. Include comment count from discovery
3. Note which repos they review
4. Document any special patterns (e.g., "uses questions instead of imperatives")
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall