Keith Mosher avatar

Keith Mosher

Community

@kmosher · San Francisco

19Followers
|
52Public Repos
|
6Published Skills

Keith Mosher publishes PR review and Claude Code skill-authoring skills covering correctness, legibility, compatibility, release engineering, and skill quality.

Skills Distribution
DomainDeveloper To...Code Review & Corr.. (35%)Claude Code Skill .. (30%)Release Engineerin.. (20%)Backward Compatibi.. (15%)

Agent Skills by Keith Mosher

Showing 6 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Keith Mosher

FAQPage Schema
What tasks can I perform using kmosher's skills?▼

You can review PRs for correctness bugs, readability problems, and backward-compatibility breaks; assess production-facing changes for rollout safety, observability gaps, and revertability; and author or tighten Claude Code skills using a test-first, economy-pass method.

Who should use these review and skill-authoring skills?▼

Software engineers performing pre-merge PR reviews, release engineers validating deployment and config changes, and developers authoring or maintaining Claude Code skills, slash commands, or plugin manifests benefit most from these skills.

How do the review skills differ from each other?▼

review-code finds correctness bugs, review-legibility handles readability cleanup after correctness is settled, review-compatibility checks caller and schema breakage, review-releng covers build/ship/observe/undo safety, and review-agent-skills applies Claude Code skill-authoring rules.

What file types does review-agent-skills cover?▼

It reviews SKILL.md, EXAMPLE.md, and PROMPT_TEMPLATE.md under skills directories, slash-command files under commands directories, and plugin manifests such as .claude-plugin/plugin.json and marketplace.json, checking frontmatter schema, triggers, voice, and eval coverage.

What is the recommended order for applying the PR review skills?▼

Settle correctness first with review-code, then check compatibility and release safety with review-compatibility and review-releng where applicable, and finish with review-legibility as the final pre-merge cleanup pass for readability issues.