Skip to content
cccskills
FreePublished on GitHub

test-driven-development

Build features or fix bugs by writing a small test first, checking that it fails for the expected reason, and making the smallest code change needed. Run related tests and review the changes for unintended effects.

OriginalShow the original description

Build or fix software with a focused red-green-refactor loop

See how to install

Good for

  • Reproducing a bug with a regression test
  • Defining expected behavior before implementing a feature
  • Checking parser, routing, or UI behavior changes

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

When to Use

Use when implementing a feature, fixing a bug, or changing behavior where a regression test can define the expected result. Prefer this workflow for parser, routing, agent-loop, and UI behavior changes.

Procedure

  1. Inspect the relevant code, existing tests, and local conventions before editing.
  2. Write the smallest regression test that demonstrates the requested behavior or reproduces the bug.
  3. Run that test and confirm it fails for the expected reason, not because the test setup is broken.
  4. Make the smallest production change that makes the test pass.
  5. Run the focused test again, then run the surrounding module suite.
  6. Review the diff for unrelated changes, brittle assertions, hidden state, and missing error paths.
  7. Report the tests run and any remaining coverage or environment limits.

Pitfalls

  • Do not write a test that only mirrors the implementation; assert the user-visible contract.
  • Do not weaken an assertion just to make a failing test pass.
  • Do not skip the focused failing-test step when the behavior is observable in a local test.
  • Keep network, filesystem, and model calls deterministic with fakes or fixtures unless the integration itself is under test.

Verification

  • The new regression test fails before the fix and passes after it.
  • The relevant focused suite passes.
  • The broader suite passes or its failure is explained with evidence.
  • The final diff contains the test and the production change needed for the same behavior.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Turn scattered messages, meeting notes, and documents into sourced action lists and status briefs. The skill reconciles updates, separates facts from tentative inferences, and highlights decisions, dependencies, risks, and unanswered questions.

  • Build a sourced action list from meeting notes
  • Combine messages and documents into a status brief
  • Assess feasibility using dependencies and blockers
odysseus-dev/odysseus94KUpdated Oct 17, 2026

Create a complete first version of a requested file or other deliverable early, then refine it and check its format, required content, location, and usability before reporting the work as finished.

  • Creating a report with all required sections
  • Saving a deliverable in a specified location
  • Checking that a generated file opens correctly
odysseus-dev/odysseus94KUpdated Oct 17, 2026

developer-docs

FreeSummary

Find official documentation for a library, framework, or API and apply it to the task at hand. Check the relevant version, distinguish documented facts from assumptions, and verify code changes with a focused test or concrete command.

  • Checking how an API or option works
  • Implementing behavior for a specific version
  • Applying official guidance to an existing project
odysseus-dev/odysseus94KUpdated Oct 17, 2026

Extract and verify text, numbers, objects, and sequences from images, documents, and video. Record where each finding appears, check exact labels and values, and build answers whose supporting evidence can be traced back to the input.

  • Extracting and checking numbers in documents
  • Tracing video events to timestamps
  • Reading and verifying labels in images
odysseus-dev/odysseus94KUpdated Oct 17, 2026

odysseus

FreeSummary

Use Claude Code to manage Odysseus tasks, email, calendar events, stored facts, and documents through a permission-scoped API. You can also start, inspect logs for, and stop Cookbook model servers using the access granted by your token.

  • Creating a task with a timed reminder
  • Reading email and preparing a reply draft
  • Saving calendar events, preferences, and documents
odysseus-dev/odysseus94KUpdated Oct 17, 2026

odysseus

FreeSummary

Use Codex to manage Odysseus todos, calendars, memory, and documents, and read or draft email. Through its permission-scoped API, the skill also supports reminders and launching, inspecting, or stopping Cookbook model servers.

  • Create a timed reminder as a todo
  • Check calendar events and add appointments
  • Read email and prepare an editable reply draft
odysseus-dev/odysseus94KUpdated Oct 17, 2026

See all skills by odysseus-dev

Report a problem with this skill