@chris1807/claude-kit 2.1.0 → 2.1.2

package/bin/cli.js

@@ -41,10 +41,28 @@ Options:
   --ado-org=<name>   Include Azure DevOps MCP for the named organization
   --global-only      Only install global agents to ~/.claude/agents/
   --help, -h         Show this help
+
+Non-interactive (CI / piped / non-TTY contexts):
+  Use --global-only OR --all --db=<...> to skip every prompt.
+  Without these flags, the installer needs a TTY and will exit early
+  rather than hang waiting on stdin.
 `);
   process.exit(0);
 }
 
+// ============================================================================
+// Non-interactive guard — fail fast instead of hanging on prompts
+// ============================================================================
+const isTTY = Boolean(process.stdin.isTTY);
+const fullyAutomated = globalOnly || (installAll && dbFlag);
+if (!isTTY && !fullyAutomated) {
+  console.error(chalk.red('\n  ✗ Non-interactive context detected (stdin is not a TTY).'));
+  console.error(chalk.yellow('  This installer needs to prompt, but cannot. Use one of:\n'));
+  console.error(chalk.gray('    npx @chris1807/claude-kit init --global-only'));
+  console.error(chalk.gray('    npx @chris1807/claude-kit init --all --db=<mongo|mssql|azuresql|postgres|none> [--ado-org=<name>]\n'));
+  process.exit(1);
+}
+
 // ============================================================================
 // Banner
 // ============================================================================

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chris1807/claude-kit",
-  "version": "2.1.0",
+  "version": "2.1.2",
   "description": "Claude Code starter kit — agents, hooks, MCP servers, slash commands, and workflow automation",
   "type": "module",
   "bin": {

package/templates/commands/implement.md

@@ -63,6 +63,12 @@ Present the plan to the user:
 ### Files to Delete (if any)
 - `path/to/old/file.cs` — {why it's being removed}
 
+### Unit Tests
+- `path/to/new.tests.cs` — covers {scenario 1}, {scenario 2}, {edge case}
+- `path/to/existing.tests.cs` — adds cases for {new behavior}
+
+List every test file you will add or modify and the scenarios each covers (happy path, error paths, edge cases, regression guards). If a change in this plan has no test coverage, justify why here.
+
 ### Agents
 - **backend**: {what it will do}
 - **frontend**: {what it will do}
@@ -111,7 +117,8 @@ Remember the `BASE_BRANCH` — you will need it for the PR step.
 ## Step 5: Implement
 
 1. **Implement** using backend and/or frontend agents according to the approved plan
-2. **Generate mockup** if there are UI changes
+2. **Write the unit tests** listed in the plan's "Unit Tests" section alongside the implementation — not after
+3. **Generate mockup** if there are UI changes
 
 ## Step 6: Build Validation
 
@@ -123,7 +130,7 @@ Run a build check **before** any other quality checks. Use the `build-validator`
 ## Step 7: Quality Checks
 
 1. **Review** code for quality, security, and Clean Architecture compliance
-2. **Run tests** — unit, integration, and build validation
+2. **Run the full test suite** — every unit test in the repo, plus integration tests. Not just the tests added in this change. A failure in an unrelated test means this change broke something else; treat it as a regression, fix it, and re-run until the entire suite is green
 3. **Run lint** — ESLint and dotnet format
 
 ## Step 8: UAT Gate

package/templates/commands/rework.md

@@ -79,6 +79,12 @@ Present the plan to the user:
 ### Files to Delete (if any)
 - `path/to/old/file.cs` — {why it's being removed}
 
+### Unit Tests
+- `path/to/new.tests.cs` — covers {scenario the rework adds or fixes}
+- `path/to/existing.tests.cs` — updates assertions for {changed behavior}
+
+List every test file you will add or modify and the scenarios each covers. Rework feedback often reveals missing test coverage on the original implementation — add regression tests that would have caught the original issue. If a rework change in this plan has no test coverage, justify why here.
+
 ### Agents
 - **backend**: {what it will do}
 - **frontend**: {what it will do}
@@ -104,7 +110,8 @@ If the PR was completed/merged and the branch was deleted, create a new branch f
 ## Step 6: Implement
 
 1. **Implement** the rework using backend and/or frontend agents according to the approved plan
-2. **Generate mockup** if there are UI changes
+2. **Write the unit tests** listed in the plan's "Unit Tests" section alongside the implementation — not after. Include any regression test that would have caught the original issue
+3. **Generate mockup** if there are UI changes
 
 ## Step 7: Build Validation
 
@@ -116,7 +123,7 @@ Run a build check **before** any other quality checks. Use the `build-validator`
 ## Step 8: Quality Checks
 
 1. **Review** code for quality, security, and Clean Architecture compliance
-2. **Run tests** — unit, integration, and build validation
+2. **Run the full test suite** — every unit test in the repo, plus integration tests. Not just the tests added in this rework. A failure in an unrelated test means this rework broke something else; treat it as a regression, fix it, and re-run until the entire suite is green
 3. **Run lint** — ESLint and dotnet format
 
 ## Step 9: UAT Gate