@chris1807/claude-kit 2.1.18 → 2.1.20

package/README.md

@@ -666,16 +666,14 @@ export MSSQL_CONNECTION_STRING="Server=localhost;Database=MyDb;User Id=sa;Passwo
 # PostgreSQL (if your project uses PostgreSQL)
 export POSTGRES_CONNECTION_STRING="postgresql://user:password@localhost:5432/mydb"
 
-# Microsoft Teams (for team notifications and messages)
-export TEAMS_TENANT_ID="your-azure-ad-tenant-id"
-export TEAMS_CLIENT_ID="your-app-registration-client-id"
-export TEAMS_CLIENT_SECRET="your-client-secret"
-
 # Stripe (if your project uses Stripe payments)
 export STRIPE_SECRET_KEY="sk_test_..."
 
 # Azure CLI (no env var needed — just log in)
 az login
+
+# Microsoft Teams (no env vars needed — uses Microsoft Graph device-code auth;
+# first invocation prints a code + URL to sign in)
 ```
 
 ### Setting Up the Teams MCP Server

package/bin/cli.js

@@ -375,7 +375,7 @@ async function main() {
     } else if (mcpChoices.db === 'mssql' || mcpChoices.db === 'azuresql') {
       mcpConfig.mcpServers.mssql = {
         command: 'npx',
-        args: ['-y', '@anthropic/mcp-mssql-server'],
+        args: ['-y', 'mssql-mcp-server'],
         env: { MSSQL_CONNECTION_STRING: '${MSSQL_CONNECTION_STRING}' },
       };
     } else if (mcpChoices.db === 'postgres') {
@@ -389,12 +389,7 @@ async function main() {
     if (mcpChoices.servers.includes('teams')) {
       mcpConfig.mcpServers.teams = {
         command: 'npx',
-        args: ['-y', '@anthropic/mcp-teams-server'],
-        env: {
-          TEAMS_TENANT_ID: '${TEAMS_TENANT_ID}',
-          TEAMS_CLIENT_ID: '${TEAMS_CLIENT_ID}',
-          TEAMS_CLIENT_SECRET: '${TEAMS_CLIENT_SECRET}',
-        },
+        args: ['-y', '@floriscornel/teams-mcp@latest'],
       };
     }
 
@@ -639,7 +634,6 @@ async function main() {
   if (dbType === 'mongo') exports.push('export MONGODB_CONNECTION_STRING="mongodb+srv://..."');
   if (dbType === 'mssql' || dbType === 'azuresql') exports.push('export MSSQL_CONNECTION_STRING="Server=...;Database=..."');
   if (dbType === 'postgres') exports.push('export POSTGRES_CONNECTION_STRING="postgresql://..."');
-  exports.push('export TEAMS_TENANT_ID="..."', 'export TEAMS_CLIENT_ID="..."', 'export TEAMS_CLIENT_SECRET="..."');
   if (selectedServers.includes('azuredevops')) exports.push('export AZURE_DEVOPS_PAT="..."  # mint at https://dev.azure.com/_usersSettings/tokens');
 
   console.log(chalk.yellow('  Environment variables to set:'));
@@ -654,6 +648,11 @@ async function main() {
   console.log(chalk.yellow('  Also run:'));
   console.log(chalk.gray('    az login'));
   console.log('');
+  if (selectedServers.includes('teams')) {
+    console.log(chalk.yellow('  Teams MCP uses Microsoft Graph device-code auth.'));
+    console.log(chalk.gray('    First use will print a code + URL to sign in. No env vars needed.'));
+    console.log('');
+  }
   console.log(`  Then: ${chalk.blue(`cd ${targetDir} && claude`)}`);
   console.log(`  Run:  ${chalk.blue('/implement AB#1234')} to start working`);
   console.log(`  Run:  ${chalk.blue('/review 142')} to review a PR`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chris1807/claude-kit",
-  "version": "2.1.18",
+  "version": "2.1.20",
   "description": "Claude Code starter kit for Azure DevOps teams — agents, hooks, MCP servers, slash commands, and end-to-end work item → PR → release → deploy workflow automation",
   "type": "module",
   "bin": {

package/templates/agents/project/deployer.md

@@ -26,8 +26,7 @@ You deploy code changes to Azure environments. Follow the standard sequence for
 2. Stage only the relevant files (never use `git add -A` — avoid committing secrets or build artifacts)
 3. Never stage `.env`, `appsettings.*.json` with real secrets, or `node_modules`
 4. Write a clear commit message explaining what changed and why
-5. Always end with: `Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>`
-6. Use HEREDOC format for the commit message
+5. Use HEREDOC format for the commit message
 
 ### Step 3: Push
 

package/templates/commands/create-work-item.md

@@ -237,6 +237,17 @@ Azure DevOps description and acceptance criteria fields are HTML — they do not
 
 Wrap each top-level section in `<p>...</p>`. Preserve any user-supplied `<img>` tags from Step 2 as-is.
 
+### Emphasis and code spans (required)
+
+A description that is one long paragraph of plain prose is not acceptable — even after Markdown is converted, the rendered output must guide the reader's eye. Before rendering, edit the draft so that:
+
+- **Key terms, values, and outcomes** in each sentence are wrapped in `**bold**` (renders as `<strong>...</strong>`). Bold the noun phrase that carries the claim, not the whole sentence.
+- **Code identifiers** — method names, class names, field names, file paths, route paths, JSON keys, env vars, commit hashes, IDs, literal values like `true` / `null` / numeric thresholds — are wrapped in `` `code spans` `` (renders as `<code>...</code>`).
+- **Lists** are used instead of comma-separated prose whenever the draft contains 2+ parallel items (steps, files, references, acceptance criteria).
+- **Section headings** (`### Description`, `### Acceptance Criteria`, etc.) are kept — they become `<h3>` and structure the rendered output.
+
+Apply this pass to every section (Description, Acceptance Criteria, Steps to Reproduce, Expected/Actual Behavior, Environment/Scope, Open Questions). Apply it equally to Bugs and User Stories.
+
 ### Call the create API
 
 Call `mcp__azure-devops__wit_create_work_item` with:

package/templates/commands/deploy.md

@@ -36,8 +36,7 @@ Wait for confirmation.
 1. Stage only the relevant files (never use `git add -A`)
 2. Never stage `.env`, `appsettings.*.json` with real secrets, or `node_modules`
 3. Commit with the provided message or auto-generated one
-4. Always end with: `Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>`
-5. Use HEREDOC format for the commit message
+4. Use HEREDOC format for the commit message
 
 ## Step 4: Push
 

package/templates/commands/rework.md

@@ -161,7 +161,23 @@ If the user provided hours (suggested or overridden):
    - **workItemType**: `Task`
    - **title**: `Rework AB#{id} — round {N}`
    - **fields**: JSON Patch document setting:
-     - `System.Description` — short summary of the rework feedback + link to the most recent PR
+     - `System.Description` — structured **HTML** (Azure DevOps does not render Markdown in this field). Use exactly these three sections, in this order, omitting any that have no content:
+
+       ```html
+       <h3>Summary</h3>
+       <p>{1–2 sentences describing the problem the rework addresses. Bold key terms, values, and outcomes with <strong>...</strong>.}</p>
+       <h3>Fix</h3>
+       <ul>
+         <li>{What changes. Wrap code identifiers, method names, fields, file paths, and literal values in <code>...</code>.}</li>
+       </ul>
+       <h3>Reference</h3>
+       <ul>
+         <li>Rework round {N} of AB#{id} ({date or tester} feedback).</li>
+         <li><a href="{PR url}">PR #{n}</a> — {one-line context, e.g. test-plan scenario, submission id in <code>...</code>}</li>
+       </ul>
+       ```
+
+       Render any code identifiers (method names, fields, file paths, hashes, literal values) inside `<code>` spans, and emphasize the key claim/value in each sentence with `<strong>`. Do not submit a wall of plain prose — every rework task must have at least the `Summary` and `Fix` sections in this shape.
      - `Microsoft.VSTS.Scheduling.OriginalEstimate` — the agreed hours
      - `Microsoft.VSTS.Scheduling.RemainingWork` — the agreed hours
      - `System.AreaPath` — same as the parent

package/templates/commands/rollback.md

@@ -54,8 +54,6 @@ Revert AB#1234, AB#1235 on {environment}
 Reverted commits:
 - abc1234: Add payment export
 - def5678: Fix login redirect
-
-Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 EOF
 )"
 ```

package/templates/infrastructure/CLAUDE-WORKFLOW.md

@@ -265,14 +265,12 @@ Each team member needs to set their own environment variables (never commit thes
 # MongoDB (required for db-admin agent)
 export MONGODB_CONNECTION_STRING="mongodb+srv://..."
 
-# Microsoft Teams (required for team notifications)
-export TEAMS_TENANT_ID="..."
-export TEAMS_CLIENT_ID="..."
-export TEAMS_CLIENT_SECRET="..."
-
 # Stripe (required when payment integration is active)
 export STRIPE_SECRET_KEY="sk_test_..."
 
 # Azure (use az login instead of env vars)
 az login
+
+# Microsoft Teams MCP — no env vars needed. First invocation prints a
+# device code + URL to sign in via Microsoft Graph (OAuth device flow).
 ```

package/templates/infrastructure/mcp.json

@@ -13,12 +13,7 @@
     },
     "teams": {
       "command": "npx",
-      "args": ["-y", "@anthropic/mcp-teams-server"],
-      "env": {
-        "TEAMS_TENANT_ID": "${TEAMS_TENANT_ID}",
-        "TEAMS_CLIENT_ID": "${TEAMS_CLIENT_ID}",
-        "TEAMS_CLIENT_SECRET": "${TEAMS_CLIENT_SECRET}"
-      }
+      "args": ["-y", "@floriscornel/teams-mcp@latest"]
     },
     "stripe": {
       "command": "npx",