Automate feature implementation from planning to GitHub pull request creation.
npx skills add https://github.com/dakotahp/dotfiles --skill feature-dakotahp
Please help me install this Agent Skill. Skill: feature Source: https://github.com/dakotahp/dotfiles/tree/main/dot_config/claude/skills/feature Command: npx skills add https://github.com/dakotahp/dotfiles --skill feature-dakotahp
This Skill provides a disciplined, end-to-end pipeline for implementing new software features with test-driven development, automated verification, and formal code review, removing ad hoc approaches that lead to unstable or unreviewed changes.
Invoke the pipeline by telling the agent to run the feature command with your description, for example: /feature add password reset flow with 1-hour expiry tokens
High-intent search queries and answers about installing and using this skill.
You can automate test-driven development by orchestrating a pipeline that generates a plan, writes failing tests, implements code via subagents, verifies with prove_it, and creates a GitHub pull request. This removes ad hoc approaches and unreviewed changes.
Automating code review and PR creation involves running code simplification, recording verification evidence, and performing formal reviews before creating a draft GitHub pull request. The pipeline iterates on review feedback until formal approvals are obtained.
Yes, you need the gh CLI and prove_it available on your PATH to run the automated TDD feature pipeline. You also need a git repository with a non-protected feature branch and the ability to run project-specific tooling like tests and linters.
A subagent-based workflow handles feature implementation by dispatching agents to write failing tests and drive code commits to a feature branch. Verification is handled by recording prove_it evidence and running code simplification before formal review.
Yes, automated TDD pipelines support optional Convext or Slack integrations during the end-to-end feature implementation process. These integrations work alongside the planning, test-driven development, and GitHub pull request creation stages.
You should avoid using an autonomous TDD feature pipeline if you lack a non-protected feature branch, do not have the gh CLI or prove_it on your PATH, or cannot install and run project-specific tooling to execute tests and linters.
franroaCreate isolated git worktrees with automated project setup and test validation.
nudgebeeMonitor GitHub pull requests for review requests and notify via macOS or Slack.
mikemylOrchestrate two-stage code review for spec compliance and quality.
JamesFincherEnforce a RED-GREEN-REFACTOR loop with pytest for Python projects.
