doctor runs eight checks, and none of them answer the question people actually have after a few weeks: has my workspace drifted from the preset it came from?
Files get edited, presets get updated, and today the only way to find out what changed is to diff by hand.
What to do
Add a check that compares each tracked file in .kiro/ against the version bundled in the installed preset, using the record in .kiro/.kiro-kit.json, and reports three categories:
- Modified locally — you changed it (usually fine, but worth knowing)
- Updated upstream — the preset has a newer version (
kiro-kit update would bring it)
- Missing — tracked but no longer on disk
Where to look
packages/cli/src/commands/doctor.ts — each check is a function returning a CheckReport; follow the shape of the existing onespackages/cli/src/core/ for the tracking file reader- Existing tests in
packages/cli/tests/unit/
Notes
Modified-locally is not an error. It should report as informational — plenty of people edit their agents on purpose, and a health check that scolds them for it is a health check people stop running.
doctorruns eight checks, and none of them answer the question people actually have after a few weeks: has my workspace drifted from the preset it came from?Files get edited, presets get updated, and today the only way to find out what changed is to diff by hand.
What to do
Add a check that compares each tracked file in
.kiro/against the version bundled in the installed preset, using the record in.kiro/.kiro-kit.json, and reports three categories:kiro-kit updatewould bring it)Where to look
packages/cli/src/commands/doctor.ts— each check is a function returning aCheckReport; follow the shape of the existing onespackages/cli/src/core/for the tracking file readerpackages/cli/tests/unit/Notes
Modified-locally is not an error. It should report as informational — plenty of people edit their agents on purpose, and a health check that scolds them for it is a health check people stop running.