User Input
$ARGUMENTS
Audience and tone (interactive mode)
When KISS_AGENT_MODE=interactive (the default), assume the user
has limited technical background and limited domain knowledge
— they may know basics but lack deep expertise in this skill's
area. Run this skill as a guided questionnaire:
- One question at a time. No walls of questions.
- Yes / no first. Phrase so
yes, no, not sure, or skip
is a valid answer.
- Translate jargon, don't strip it. Use the technical term but
always pair it with a plain-English gloss the first time it
appears.
- Choices, not blank fields. When yes/no isn't enough, offer
2-4 lettered options (A/B/C/D) with one-line plain-language
descriptions of the trade-off. Always include "Not sure — pick
a sensible default".
- Always recommend. State the option you would pick and why in
one sentence so the user can reply "yes" / "ok" to accept. Pull
defaults from upstream artefacts (spec, architecture, ADRs,
standards) before asking blank.
- Show, don't ask. When upstream artefacts already imply an
answer, propose it as a pre-filled finding and ask for a
yes / no confirmation rather than asking the user to fill in a
blank.
not sure / skip triggers a sensible default, marked
"(default applied — confirm later)" in the artefact, and a debt
entry in this skill's debt file.
When KISS_AGENT_MODE=auto (or --auto), skip the questionnaire
entirely: apply sensible defaults from upstream artefacts and log
decisions to the parent agent's decision log.
Inputs
.kiss/context.yml{context.paths.docs}/bugs/BUG-*.md{context.paths.docs}/testing/regression-index.md
Outputs
{context.paths.docs}/bugs/change-register.md{context.paths.docs}/bugs/change-register.extract
Context Update
Does not mutate .kiss/context.yml.
Handoffs
kiss-regression-tests cross-references each closed bug.kiss-status-report pulls counts for the status summary.kiss-deployment reviews the register when assembling release
notes.
AI authoring scope
Does: append one row per applied fix with bug id, commit,
files, regression-test id, reviewer; update the source bug file's
status to "Closed" once the user confirms.
Does not: write code, push commits, close bugs without the
user's explicit confirmation of commit + reviewer.
Usage
<SKILL_DIR> = the integration's skills root (e.g. .claude/skills/
for Claude Code, .agents/skills/ for Antigravity / Codex,
.cursor/skills/ for Cursor, .windsurf/workflows/ for Windsurf).
Scripts live at <SKILL_DIR>/<skill-name>/scripts/….
CR_BUG_ID=BUG-014 CR_COMMIT=abc123 CR_PR=#512 \
CR_FILES="src/email.ts;tests/regression/bug-014.test.ts" \
CR_REGRESSION_TEST="tests/regression/bug-014.test.ts" \
CR_REVIEWER="tech-lead" \
bash <SKILL_DIR>/kiss-change-log/scripts/bash/record-fix.sh --auto
Answer keys
| Key |
Meaning |
Default |
CR_BUG_ID |
bug fixed |
(required) |
CR_COMMIT |
commit SHA (short or long) |
(required) |
CR_PR |
PR reference (#512) |
empty |
CR_FILES |
;-separated files touched |
empty |
CR_REGRESSION_TEST |
path to new regression test |
empty (→ debt) |
CR_REVIEWER |
who reviewed / approved |
(required) |
1---2name: kiss-change-log-23description: Maintains the change register — one row per applied bug-fix — with bug id, commit/PR, files touched, regression test, and the reviewer. Records what actually shipped; does not ship anything. Use when recording a bug fix that has shipped, updating the change log after a release, or tracking which commits fixed which bugs.4---567## User Input89```text10$ARGUMENTS11```1213## Audience and tone (interactive mode)1415When `KISS_AGENT_MODE=interactive` (the default), assume the user16has **limited technical background and limited domain knowledge**17— they may know basics but lack deep expertise in this skill's18area. Run this skill as a guided questionnaire:1920- **One question at a time.** No walls of questions.21- **Yes / no first.** Phrase so `yes`, `no`, `not sure`, or `skip`22 is a valid answer.23- **Translate jargon, don't strip it.** Use the technical term but24 always pair it with a plain-English gloss the first time it25 appears.26- **Choices, not blank fields.** When yes/no isn't enough, offer27 2-4 lettered options (A/B/C/D) with one-line plain-language28 descriptions of the trade-off. Always include "Not sure — pick29 a sensible default".30- **Always recommend.** State the option you would pick and why in31 one sentence so the user can reply "yes" / "ok" to accept. Pull32 defaults from upstream artefacts (spec, architecture, ADRs,33 standards) before asking blank.34- **Show, don't ask.** When upstream artefacts already imply an35 answer, propose it as a pre-filled finding and ask for a36 yes / no confirmation rather than asking the user to fill in a37 blank.38- **`not sure` / `skip` triggers a sensible default**, marked39 "(default applied — confirm later)" in the artefact, and a debt40 entry in this skill's debt file.4142When `KISS_AGENT_MODE=auto` (or `--auto`), skip the questionnaire43entirely: apply sensible defaults from upstream artefacts and log44decisions to the parent agent's decision log.4546## Inputs4748- `.kiss/context.yml`49- `{context.paths.docs}/bugs/BUG-*.md`50- `{context.paths.docs}/testing/regression-index.md`5152## Outputs5354- `{context.paths.docs}/bugs/change-register.md`55- `{context.paths.docs}/bugs/change-register.extract`5657## Context Update5859Does not mutate `.kiss/context.yml`.6061## Handoffs6263- `kiss-regression-tests` cross-references each closed bug.64- `kiss-status-report` pulls counts for the status summary.65- `kiss-deployment` reviews the register when assembling release66 notes.6768## AI authoring scope6970**Does:** append one row per applied fix with bug id, commit,71files, regression-test id, reviewer; update the source bug file's72status to "Closed" once the user confirms.7374**Does not:** write code, push commits, close bugs without the75user's explicit confirmation of commit + reviewer.7677## Usage7879> `<SKILL_DIR>` = the integration's skills root (e.g. `.claude/skills/`80> for Claude Code, `.agents/skills/` for Antigravity / Codex,81> `.cursor/skills/` for Cursor, `.windsurf/workflows/` for Windsurf).82> Scripts live at `<SKILL_DIR>/<skill-name>/scripts/…`.8384```bash85CR_BUG_ID=BUG-014 CR_COMMIT=abc123 CR_PR=#512 \86CR_FILES="src/email.ts;tests/regression/bug-014.test.ts" \87CR_REGRESSION_TEST="tests/regression/bug-014.test.ts" \88CR_REVIEWER="tech-lead" \89 bash <SKILL_DIR>/kiss-change-log/scripts/bash/record-fix.sh --auto90```9192### Answer keys9394| Key | Meaning | Default |95|---|---|---|96| `CR_BUG_ID` | bug fixed | *(required)* |97| `CR_COMMIT` | commit SHA (short or long) | *(required)* |98| `CR_PR` | PR reference (#512) | empty |99| `CR_FILES` | `;`-separated files touched | empty |100| `CR_REGRESSION_TEST` | path to new regression test | empty (→ debt) |101| `CR_REVIEWER` | who reviewed / approved | *(required)* |
dauquangthanh 