change

Automates code changes from stories or issues with test-first development and review.

3|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill change-cwijayasundara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/change
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill change-cwijayasundara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of changing behavior in existing code, providing two main approaches: story-driven and issue-based. It streamlines the process of modifying code to add new features, fix bugs, or improve functionality.

Core Features & Use Cases

  • Story-Driven: Automates the process of adding new features or improving existing ones based on user stories.
  • Issue-Based: Automates the process of fixing bugs reported in issue tracking systems like GitHub.
  • Test-First Development: Ensures that no code is committed until tests have been written and passed.
  • Code Review: Integrates code review processes to ensure code quality and adherence to standards.
  • Use Case: For example, when a new feature needs to be added to a codebase, the developer can use this Skill to automate the process of writing tests, implementing the feature, and reviewing the changes.

Quick Start

Use the 'change' skill to implement a new feature by specifying the feature description or story ID.

Frequently Asked Questions about change

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

FAQPage Schema
How do I automate behavior changes in existing code?

You can automate behavior changes in existing code by using story-driven or issue-based approaches. This ensures test-first development and integrates code review processes to maintain software quality standards.

What is the best way to implement new features from user stories?

Using a story-driven approach is the best way to implement new features from user stories. It streamlines the process of modifying code, writing tests first, and integrating code reviews to ensure quality.

Can I automate bug fixing from GitHub issues?

Yes, you can automate bug fixing from GitHub issues using an issue-based approach. It integrates with issue tracking systems to automate the required code modifications and ensure test-first development.

Does test-first development prevent code commits before tests pass?

Yes, test-first development ensures that no code is committed until tests have been written and passed. This strict requirement guarantees that new features and bug fixes maintain code quality.

Do I need issue tracking systems to automate code changes?

You need issue tracking systems like GitHub when using the issue-based approach for bug fixing. The story-driven approach alternatively relies on user stories to automate feature development.

Are code review processes included when modifying existing software?

Yes, code review processes are integrated when modifying existing software. This ensures that automated behavior changes, feature additions, and bug fixes adhere to established code quality standards.