PR Custody

Add dev-skills: language-agnostic development workflow suite

@phbpxchecks n/achecks…add-dev-skills → master2 files · +162 −0updated 2mo ago

▸Description

What problem does this skill solve?

Development workflows in Claude Code lack structured discipline - developers jump between coding, testing, reviewing, and committing without a consistent process. This leads to missed tests, sloppy commits, and incomplete code reviews.

dev-skills provides 10 interconnected skills that enforce good practices (TDD, root-cause debugging, atomic commits, multi-perspective code review) while staying lightweight - no enterprise gates or mandatory pipelines.

What's included

Skill	What it does
`dev-brainstorm`	Validate ideas and design solutions before writing any code
`dev-plan`	Write a detailed implementation plan saved to `docs/plans/`
`dev-plan-issue`	Read a GitHub issue and produce an implementation plan from it
`dev-do`	Execute an approved plan task by task with test validation
`dev-tdd`	Implement features using RED-GREEN-REFACTOR discipline
`dev-debug`	Investigate bugs by finding root causes first
`dev-review`	Run a 4-perspective code review in parallel
`dev-commit`	Organize changes into clean, atomic Conventional Commits
`dev-pr`	Create a GitHub pull request with auto-generated title and description
`dev-explore`	Understand an unfamiliar codebase through parallel exploration

Key differentiators

Language-agnostic - Auto-detects Go, Python, TypeScript, Rust, Java, etc.
Plan-driven - Separates design from implementation with persistent, reviewable plans
Parallel agents - Uses simultaneous exploration and review to avoid tunnel vision
Works standalone - Each skill works independently, no dependencies between them

Example workflow

/dev-brainstorm → /dev-plan → /dev-do → /dev-review → /dev-commit → /dev-pr

Testing

Tested on Claude Code across Go, Python, and TypeScript projects.

Source: https://github.com/phbpx/dev-skills

loading diff…