code

Guide end-to-end coding workflows with tests-first implementation and mutation testing.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill code-droxey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code
Source: https://github.com/droxey/skills/tree/main/code
Command: npx skills add https://github.com/droxey/skills --skill code-droxey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes evals (resource) and agents (resource) components.

What problem does it solve?

This Skill reduces regressions in non-trivial code changes by forcing a disciplined plan/spec/test/verify/review process that includes mutation-testing-style validation.

Core Features & Use Cases

It fits refactors, feature development, and multi-file production changes where quality gates matter more than speed. It emphasizes early risk discovery, explicit acceptance criteria, tests-first implementation, manual verification of key paths, and a review pass strengthened by mutation testing. It also ensures impacted documentation and operational artifacts stay consistent with the delivered behavior.

Quick Start

Use the code skill to run your coding task through a discussion-to-closeout workflow with tests-first implementation, manual verification, and mutation testing evidence included.

Frequently Asked Questions about code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce regressions when doing non-trivial software refactoring?

A tests-first coding workflow reduces regressions by requiring explicit acceptance criteria, structured manual verification, and mutation testing-style assurance before closeout, ensuring non-trivial changes are validated.

What is mutation testing and how does it fit into a coding workflow?

Mutation testing validates test suite strength by verifying that tests fail when code is altered. In a coding workflow, it serves as a post-implementation review gate to harden quality before closeout.

How do I implement a tests-first workflow for feature development?

Start by creating a spec with explicit acceptance criteria, then write tests aligned to those criteria before delivering the feature implementation, followed by structured manual verification of key paths.

Does this coding workflow require manual verification after writing tests?

Yes, the coding workflow requires structured manual verification of key paths after tests-first delivery, ensuring the implementation behaves correctly before proceeding to the mutation-testing-style review phase.

When should I use a spec writing and mutation testing workflow for software changes?

Use this workflow for multi-file production changes, refactors, and feature implementations where quality gates matter more than speed, requiring early risk discovery and regression prevention.