defprod-untracked-change

Runs quality-gated code, test, review, and land stages for decision-free changes without creating change records.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-untracked-change-defprod1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defprod-untracked-change
Source: https://github.com/defprod1/defprod-skills/tree/main/skills/defprod-untracked-change
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-untracked-change-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small, decision-free edits like label tweaks, lint fixes, and comment tidy-ups do not deserve a tracked change record, but skipping quality gates entirely turns them into risky raw commits. This Skill provides a workflow for recordless work that keeps code, test, and review gates intact while creating no change record, no stage stamps, and no Change trailer. ## Core Features & Use Cases - Recordless quality-gated workflow: Reuses the standard code, test, review, and land stage skills in a context-free mode so nothing is stamped and no CHG record is created. - Escalation tripwires: Detects when a design decision, product definition change, or trackable decision appears and hands off to the tracked change workflow instead. - Stale context self-healing: Checks for leftover change-context carriers (context file, branch naming, commit trailer) and cleans up stale ones before proceeding. - Use Case: You need to rename a button label and fix lint warnings across a few files. This Skill verifies the edits do not contradict any user story acceptance criteria, runs the test and review gates, and lands the work as an ordinary conventional commit with no change record. ## Quick Start Ask the agent to make a small decision-free edit such as a copy tweak or lint fix using the untracked change workflow so it lands without a change record.

Frequently Asked Questions about defprod-untracked-change

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

FAQPage Schema
How do I make a small code edit without creating a change record?

Use the untracked change workflow for decision-free edits like label tweaks, lint fixes, or comment tidy-ups. It runs the standard code, test, review, and land stages but creates no change record, no stage stamps, and no Change commit trailer.

When should I use a tracked change instead of an untracked change?

Escalate to the tracked change workflow whenever a real design decision is involved, the product definition must change, or the work carries a decision the business should know. When unsure, prefer the tracked route since a record is cheap to create.

Does the untracked change workflow skip tests and code review?

No, test and review gates always run. Running these quality gates is the entire difference between this workflow and a bare git commit, so they are never skipped.

What happens if a change context already exists in the worktree?

The workflow checks for a context file, a chg-prefixed branch, or a Change commit trailer. An active tracked change stops the run, while a stale shipped or cancelled context is deleted automatically before proceeding.

Can the untracked change workflow edit user stories or product definitions?

No, its alignment step is strictly read-only against areas and user stories. If the work requires creating or editing any definition entity, that is an escalation tripwire and the work hands off to the tracked change workflow.