PeteRichardson
Community@PeteRichardson
PeteRichardson maintains 18 Claude Code skills covering the full GitHub development lifecycle: code review, issue triage, PR sequencing, testing, documentation, and commit preparation.
Agent Skills by PeteRichardson
Showing 18 vetted skills indexed across 1 GitHub repositories.
supacode-cli
Control Supacode worktrees, tabs, and terminal surfaces from the command line.
pipeline
Reports repository position in the review-to-merge pipeline and names the next command.
design-doc
Generate a living technical design document from an existing codebase.
update-docs
Assess whether design documentation needs updating based on recent git changes and update it.
project-review
Audits an entire codebase for tech debt and writes a cited findings report to docs/reviews/PROJECT_REVIEW.md.
pr-triage
Ranks open GitHub pull requests into a merge order that minimizes total rebase and conflict work.
comment
Insert descriptive comments and docstrings into code without modifying any logic.
supacode-deeplinks
Control Supacode worktrees, tabs, and repositories via supacode:// deeplink URLs.
code-review
Reviews code scopes or GitHub pull requests and generates ranked markdown issue reports.
add-tests
Analyze code changes, identify test coverage gaps, and write approved tests for Rust, Swift, and Python.
onote
Summarize Claude sessions into structured Obsidian-ready markdown notes with YAML frontmatter.
issue-triage
Assess open GitHub issues and produce an ordered fix plan with per-issue dispositions.
readme
Generates a README.md from codebase structure, manifests, and CLI definitions.
work-issue
Automates GitHub issue resolution through worktree-based branches, PR creation, and per-issue resolution comments.
make-issues
Convert code review findings into labeled, deduplicated GitHub issues.
run-tests
Detect the test framework, run the test suite, and report pass or failure results.
pre-commit
Verifies test coverage, test results, and documentation currency before generating a commit message.
commit-message
Generate conventional commit messages from staged or changed git files.
Frequently Asked Questions About PeteRichardson
FAQPage SchemaWhat tasks can I accomplish with PeteRichardson's skills?▼
The 18 skills cover the review-to-merge lifecycle: auditing codebases for tech debt, reviewing PRs across HIGH/IDIOM/MEDIUM/LOW severity categories, triaging and ordering GitHub issues and PRs, generating READMEs and design docs, planning test coverage, running test suites, and producing conventional commit messages.
Who are these skills designed for?▼
Software engineers and maintainers working in GitHub repositories with Claude Code, especially those managing multiple open PRs, inheriting unfamiliar codebases, or wanting structured review-to-issue-to-PR pipelines with worktree isolation and per-issue resolution comments.
How do the pipeline and triage skills work in practice?▼
The pipeline skill reads artifacts left by each stage (docs/reviews/, fingerprinted issues, .claude/tmp/ snapshots, Fix-I branches, open PRs) to report position and name the next command. Issue-triage and pr-triage produce advisory snapshots with relationship graphs and merge ordering; they never mutate state except an optional status label.
Are these skills safe to run on a live repository?▼
Yes, most are advisory-only. Code-review, project-review, pr-triage, and issue-triage create markdown snapshots without modifying code. Mutating skills like work-issue and make-issues act explicitly: creating branches, PRs, labels, and resolution comments only when invoked, with add-tests requiring plan approval first.
What prerequisites do these skills require?▼
A GitHub-backed repository and a Claude Code environment. Supacode-specific skills (supacode-cli, supacode-deeplinks) require the Supacode terminal, with deeplinks as fallback where the CLI is unavailable. The onote skill targets Obsidian vaults, producing YAML-frontmatter markdown notes from session content.