@wbern/claude-instructions 1.7.0 → 1.8.1

package/downloads/without-beads/red.md

@@ -1,21 +1,23 @@
 ---
 allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute TDD Red Phase - write ONE failing test
+argument-hint: [optional additional info]
 ---
 
 RED PHASE! Apply the below to the info given by user input here:
 
 $ARGUMENTS
 
-(If there was no info above, use info from the current context of conversation. If there was not enough info, ask for it.)
-
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
+(If there was no info above, fallback to the context of the conversation)
+
 ## TDD Fundamentals
 
 ### The TDD Cycle

package/downloads/without-beads/refactor.md

@@ -9,13 +9,12 @@ Apply this document (specifically the Refactor phase), to the info given by user
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-(If there was no info above, fallback to:
-1. Context of the conversation, if there's an immediate thing
-2. `bd ready` to see what to work on next and start from there)
+(If there was no info above, fallback to the context of the conversation)
 
 ## TDD Fundamentals
 
@@ -88,3 +87,5 @@ This phase is **not part of the regular TDD workflow** and must only be applied
 - In the refactor phase, it is perfectly fine to refactor both test and implementation code. That said, completely new functionality is not allowed. Types, clean up, abstractions, and helpers are allowed as long as they do not introduce new behavior.
 - Adding types, interfaces, or a constant in order to replace magic values is perfectly fine during refactoring.
 - Provide the agent with helpful directions so that they do not get stuck when blocking them.
+
+1. **Consistency check** - Look for inconsistent patterns, naming conventions, or structure across the codebase

package/downloads/without-beads/ship.md

@@ -9,6 +9,7 @@ argument-hint: [optional-commit-message]
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
@@ -86,4 +87,3 @@ If tests fail, linter fails, or changes are large/complex, STOP and suggest:
 
 - Use `/show` for changes that should be seen but don't need approval
 - Use `/ask` (traditional PR) for complex changes needing discussion
-

package/downloads/without-beads/show.md

@@ -9,6 +9,7 @@ argument-hint: [optional-pr-title-and-description]
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
@@ -102,4 +103,3 @@ Use **Show** when:
 Use **/ship** instead if: change is tiny and obvious (typo, formatting)
 
 Use **/ask** instead if: change needs discussion, breaks APIs, or you're uncertain
-

package/downloads/without-beads/spike.md

@@ -11,13 +11,12 @@ $ARGUMENTS
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-(If there was no info above, fallback to:
-1. Context of the conversation, if there's an immediate thing
-2. `bd ready` to see what to work on next and start from there)
+(If there was no info above, fallback to the context of the conversation)
 
 ## TDD Fundamentals
 

package/downloads/without-beads/summarize.md

@@ -1,8 +1,17 @@
 ---
 allowed-tools: AskUserQuestion
 description: Summarize conversation progress and next steps
+argument-hint: [optional additional info]
 ---
 
+## General Guidelines
+
+### Output Style
+
+- **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
+- Write natural, descriptive code without meta-commentary about the development process
+- The code should speak for itself - TDD is the process, not the product
+
 Create a concise summary of the current conversation suitable for transferring context to a new conversation.
 
 Additional info: $ARGUMENTS
@@ -12,16 +21,19 @@ Additional info: $ARGUMENTS
 Provide a summary with these sections:
 
 ### What We Did
+
 - Key accomplishments and changes made
 - Important decisions or discoveries
 - Files created, modified, or analyzed
 
 ### What We're Doing Next
+
 - Immediate next steps
 - Pending tasks or work in progress
 - Goals or objectives to continue
 
 ### Blockers & User Input Needed
+
 - Any issues requiring user intervention
 - Decisions that need to be made
 - Missing information or clarifications needed
@@ -29,4 +41,3 @@ Provide a summary with these sections:
 ## Output Format
 
 Keep the summary concise and actionable - suitable for pasting into a new conversation to quickly restore context without needing the full conversation history.
-

package/downloads/without-beads/tdd.md

@@ -9,6 +9,7 @@ argument-hint: [optional-response-to-last-message]
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product

package/downloads/without-beads/worktree-add.md

@@ -9,6 +9,7 @@ argument-hint: <branch-name-or-github-issue-url> [optional-base-branch]
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
@@ -72,7 +73,7 @@ Uncommitted changes: !git status --short`
     <input>The user-provided arguments</input>
     <expected_format>branch-name-or-github-url [optional-base-branch]</expected_format>
     <example>fix/issue-123-main-content-area-visually-clipped main</example>
-    <example_github_url>https://github.com/owner/project/issues/123 main</example_github_url>
+    <example_github_url><https://github.com/owner/project/issues/123> main</example_github_url>
     <default_base_branch>main (if not specified)</default_base_branch>
   </step_1>
 
@@ -182,7 +183,7 @@ Uncommitted changes: !git status --short`
       - packages/*/.env.local
       - (any other .env.local files found)
     </common_locations>
-    <copy_command>find . -name ".env.local" -type f -exec sh -c 'mkdir -p "$(dirname "${parent_path}/${branch_name}/$1")" && cp "$1" "${parent_path}/${branch_name}/$1"' _ {} \;</copy_command>
+    <copy_command>find . -name ".env.local" -type f -exec sh -c 'mkdir -p "$(dirname "${parent_path}/${branch_name}/$1")" && cp "$1" "${parent_path}/${branch_name}/$1"' _{} \;</copy_command>
     <purpose>Preserve local environment configurations for development</purpose>
     <note>Only copies files that exist; ignores missing ones</note>
   </step_9>
@@ -249,14 +250,15 @@ EOF</create_file_command>
 </execution_steps>
 
 <important_notes>
-  - Automatically detects and uses your current IDE (VS Code, VS Code Insiders, Cursor, Zed, etc.)
-  - Creates VS Code-specific tasks.json only for VS Code variants (auto-starts Claude on folder open)
-  - Branch names with slashes (feat/, fix/, etc.) are fully supported
-  - The worktree directory path will match the full branch name including slashes
-  - Settings are copied to maintain the same permissions across worktrees
-  - Environment files (.env.local) are copied to preserve local configurations
-  - Each worktree has its own node_modules installation
-  - Uncommitted changes are automatically stashed and moved to the new worktree
-  - Your work-in-progress seamlessly transfers to the new branch
-  - IDE detection fallback: checks available editors and uses priority order
-</important_notes>
+
+- Automatically detects and uses your current IDE (VS Code, VS Code Insiders, Cursor, Zed, etc.)
+- Creates VS Code-specific tasks.json only for VS Code variants (auto-starts Claude on folder open)
+- Branch names with slashes (feat/, fix/, etc.) are fully supported
+- The worktree directory path will match the full branch name including slashes
+- Settings are copied to maintain the same permissions across worktrees
+- Environment files (.env.local) are copied to preserve local configurations
+- Each worktree has its own node_modules installation
+- Uncommitted changes are automatically stashed and moved to the new worktree
+- Your work-in-progress seamlessly transfers to the new branch
+- IDE detection fallback: checks available editors and uses priority order
+</important_notes>

package/downloads/without-beads/worktree-cleanup.md

@@ -9,6 +9,7 @@ argument-hint: (no arguments)
 ## General Guidelines
 
 ### Output Style
+
 - **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
@@ -212,17 +213,18 @@ Current worktrees: !git worktree list`
 </execution_steps>
 
 <important_notes>
-  - Uses GitHub PR merge status as the ONLY reliable way to verify if a branch was merged
-  - DOES NOT use "git branch --merged" command as it's unreliable for merge verification
-  - Only processes branches with PRs that were definitively merged to main
-  - Skips worktrees without merged PRs and continues to next oldest candidate
-  - Checks and optionally closes related GitHub issues
-  - Prioritizes oldest worktrees by directory age first for systematic cleanup
-  - Warns about very recent worktrees (created within 24 hours) to avoid cleaning active work
-  - Preserves useful development settings before deletion
-  - Requires explicit confirmation before any destructive actions
-  - Handles locked worktrees automatically
-  - Processes one worktree at a time to maintain control
-  - Must be run from main branch for safety
-  - Works with standard GitHub repository URLs (owner/repo format)
-</important_notes>
+
+- Uses GitHub PR merge status as the ONLY reliable way to verify if a branch was merged
+- DOES NOT use "git branch --merged" command as it's unreliable for merge verification
+- Only processes branches with PRs that were definitively merged to main
+- Skips worktrees without merged PRs and continues to next oldest candidate
+- Checks and optionally closes related GitHub issues
+- Prioritizes oldest worktrees by directory age first for systematic cleanup
+- Warns about very recent worktrees (created within 24 hours) to avoid cleaning active work
+- Preserves useful development settings before deletion
+- Requires explicit confirmation before any destructive actions
+- Handles locked worktrees automatically
+- Processes one worktree at a time to maintain control
+- Must be run from main branch for safety
+- Works with standard GitHub repository URLs (owner/repo format)
+</important_notes>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wbern/claude-instructions",
-  "version": "1.7.0",
+  "version": "1.8.1",
   "description": "TDD workflow commands for Claude Code CLI",
   "type": "module",
   "bin": "./bin/cli.js",
@@ -50,6 +50,7 @@
     "knip": "^5.70.2",
     "lint-staged": "^16.2.7",
     "markdown-magic": "^4.0.4",
+    "markdownlint-cli": "^0.46.0",
     "prettier": "^3.7.2",
     "tsup": "^8.5.1",
     "tsx": "^4.20.6",