This file documents reusable implementation skills for this repository. Each skill includes trigger conditions, key files, and completion checks.
Use when:
- Adding or changing a
devcommand. - Updating command arguments or dispatch logic.
Touchpoints:
src/dev.ps1src/commands/*.ps1
Checklist:
- Keep action routing in
switch ($action)consistent. - Update help text when command syntax changes.
- Keep command functions in their dedicated module file.
- Preserve existing action names unless migration is explicit.
Validation:
- Dot-source entry point:
. .\src\dev.ps1 - Run
dev helpand verify updated usage text.
Use when:
- Editing settings behavior (
code,explorer, roots, defaults). - Modifying config read/write logic.
Touchpoints:
src/core/Config.ps1src/commands/Set.ps1
Checklist:
- Keep config schema backward compatible where possible.
- Handle missing config files with safe defaults.
- Validate root names and paths before persisting.
Validation:
- Test
dev set --code=true/false. - Test
dev set --explorer=true/false. - Test
dev set root <name> <path>and removal flow.
Use when:
- Updating
pull,release,local-release,status, orinit.
Touchpoints:
src/commands/Git.ps1src/dev.ps1
Checklist:
- Keep destructive operations explicit and user-visible.
- Preserve branch handling behavior for
dev init. - Keep local and remote release behavior clearly separated.
Validation:
- Test commands in a temporary git repo.
- Verify failure messaging for invalid repo states.
Use when:
- Shipping a new version.
- Updating installer/package metadata.
Touchpoints:
inno/setup.isschocolatey/dev-ps-utils.nuspecweb/app/releases/releases.jsonrelease-notes/RELEASE-NOTE-v*.md
Checklist:
- Sync version string across all release files.
- Add release note file for the new version.
- Add release entry to website releases JSON.
Validation:
- Confirm all version references match exactly.
- Ensure release notes mention user-facing changes.
Use when:
- Updating user documentation or docs pages.
- Adding command examples or installation changes.
Touchpoints:
README.mdweb/app/docs/page.tsxweb/components/*.tsx
Checklist:
- Keep examples executable as shown.
- Reflect current CLI options and defaults.
- Preserve existing site architecture and component boundaries.
Validation:
- Check that docs do not contradict command help text.
- Run web build/test flow when making substantial web changes.
Use when:
- Updating browser extension behavior or host messaging.
Touchpoints:
chrome-extension/background.jschrome-extension/popup.jschrome-extension/native-host/*.ps1chrome-extension/native-host/install.ps1
Checklist:
- Keep message payload shapes stable.
- Ensure native host scripts are path-safe on Windows.
- Maintain manifest permissions at minimum required scope.
Validation:
- Verify extension startup and popup actions.
- Verify host connection and command execution flow.