why

Document code changes with rationale in markdown files.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/jsalio/My-sdd-flow --skill why-jsalio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: why
Source: https://github.com/jsalio/My-sdd-flow/tree/main/why
Command: npx skills add https://github.com/jsalio/My-sdd-flow --skill why-jsalio

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ensures that every code change is documented with its rationale, fostering knowledge retention and codebase clarity.

Core Features & Use Cases

  • Change Documentation: Captures the reasons, decisions, and technical debt associated with code changes.
  • Commit Message Generation: Constructs structured commit messages linking changes back to their original specifications.
  • Traceability: Enables easier comprehension of the evolution of the codebase over time.

Quick Start

Use the /why command to document why a new feature 'user-profile' was implemented.

Frequently Asked Questions about why

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

FAQPage Schema
How do I document the rationale behind code changes for better traceability?

To document the rationale behind code changes for traceability, you can use structured markdown files to capture decisions, reasons, and technical debt, ensuring codebase clarity and knowledge retention over time.

What is the best way to generate structured commit messages linking back to specifications?

The best way to generate structured commit messages linking back to specifications is to document the specific decisions and reasons for a change first, which then constructs clear, traceable commit messages automatically.

How does logging technical debt and decisions improve codebase management?

Logging technical debt and decisions improves codebase management by providing structured documentation of why changes were made, fostering knowledge retention and enabling easier comprehension of the codebase evolution.

Do I need to provide specific input details to document a code change?

Yes, you need to provide specific user input details about the change to document its rationale effectively, which ensures the resulting structured commit messages and markdown records accurately reflect the actual codebase modifications.

Can I use markdown files for recording code change decisions and technical debt?

Yes, you can use markdown files for recording code change decisions and technical debt, which provides a structured format for capturing the specific reasons and technical context behind your codebase modifications.