Enforce test-driven development with tests before code and 80% coverage.
npx skills add https://github.com/devsepnine/hibi_ai --skill tdd-workflow-devsepnine
Please help me install this Agent Skill. Skill: tdd-workflow Source: https://github.com/devsepnine/hibi_ai/tree/main/src/skills/tdd-workflow Command: npx skills add https://github.com/devsepnine/hibi_ai --skill tdd-workflow-devsepnine
Writing code without a safety net often leads to regressions and unclear requirements. This skill enforces test-driven development to ensure features are implemented with verified tests and measurable coverage.
Start by outlining a user journey for the feature, then write corresponding unit, integration, and end-to-end tests before implementing the feature.
High-intent search queries and answers about installing and using this skill.
Test-driven development is enforced by requiring tests before code implementation for features, bug fixes, and refactors. You start by outlining user journeys, writing unit, integration, and e2e tests, and then implementing the code to achieve 80%+ coverage.
A structured TDD workflow defines user journeys first, writes corresponding tests, runs them, implements the feature code, and finally verifies coverage. This ensures internal logic, API interactions, and end-to-end user workflows are reliably tested.
Yes, the TDD workflow supports testing scenarios using Vitest and Playwright. It applies these frameworks to cover unit tests, integration tests, and end-to-end testing across new features, bug fixes, and API changes.
Yes, the test-first workflow applies to writing new features, bug fixes, refactors, and API changes. It enforces defining tests first and verifying code reliability across all these development scenarios to prevent regressions.
Defining user journeys before writing tests provides a repeatable workflow structure. It clarifies requirements upfront, ensuring the unit, integration, and end-to-end tests accurately reflect desired user workflows before code implementation begins.
The TDD process requires achieving 80% or higher overall test coverage. This measurable coverage threshold ensures features are implemented with verified tests, providing a safety net against regressions and unclear requirements.
memorysaverAutomate end-to-end testing for PaperLens features with scripted gates, BDD journeys, and API drivers.
fideguchEnforce test-driven development workflows with unit, integration, and end-to-end tests.
epicweb-devAutomate Epic Stack testing with Vitest and Playwright.
klu-devEnforce the TDD lifecycle of test creation, implementation, refactoring, and coverage verification.
