Coordinate GitHub issue-driven feature work with a strict TDD workflow.
npx skills add https://github.com/Bahm/spaced-learning --skill implement-issue-bahm
Please help me install this Agent Skill. Skill: implement-issue Source: https://github.com/Bahm/spaced-learning/tree/main/.claude/skills/implement-issue Command: npx skills add https://github.com/Bahm/spaced-learning --skill implement-issue-bahm
This Skill standardizes and enforces a TDD-first workflow to implement issues, ensuring failed tests drive implementation and that knowledge is auditable through memory/core docs and canonical CLAUDE.md.
Describe the issue, run failing tests, implement the fix, verify with tests, and submit a PR following the TDD workflow.
High-intent search queries and answers about installing and using this skill.
To implement a GitHub issue with TDD, write failing tests for the requested feature before any code, implement the fix to pass the tests, verify the changes, and submit a pull request. This enforces test-first development from issue comprehension to PR creation.
Test-driven issue workflow automation standardizes feature implementation by enforcing a strict TDD cycle. It guides you from reading the issue and writing failing tests to implementing domain logic, verifying with tests, and documenting changes to ensure auditable, test-first development.
You maintain living documentation by promoting lessons learned during issue implementation to canonical docs like CLAUDE.md. This knowledge hygiene practice preserves project knowledge and ensures documentation updates happen automatically after each TDD session.
Yes, issue-driven development enforces pull request discipline by requiring steps for domain logic, test verification, and documentation updates before PR submission. It ensures failed tests drive implementation and that knowledge remains auditable through core docs.
The best way to coordinate feature work is using an end-to-end TDD workflow. This governs the entire process from issue comprehension to PR creation, ensuring you write failing tests first, implement the fix, verify changes, and update canonical documentation.
No, you do not need existing tests. The TDD-driven issue workflow starts by writing new failing tests for the specific issue before implementing any code, ensuring the requested feature or fix is test-first and properly verified before submitting a pull request.
elijahmurrayConfigure GitHub Issues, Linear, Jira, or GitLab for issue tracking.
bacchus-labsReview documentation pull requests against issue requirements and code accuracy.
Kushal9889Sets up Husky git hooks to automate code quality checks and testing before commits.
greyhaven-aiCoordinate multi-agent TDD workflows enforcing red-green-refactor discipline across Python and TypeScript.
