npm - thanh-kit - Versions diffs - 2.5.1 → 2.5.2 - Mend

thanh-kit 2.5.1 → 2.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (123) hide show

package/dist/index.js +20 -61
package/dist/index.js.map +1 -1
package/package.json +1 -1
package/templates/{commands → command-archive}/ask.md +5 -5
package/templates/{commands → command-archive}/ck-help.md +18 -2
package/templates/command-archive/docs/init.md +38 -0
package/templates/command-archive/docs/summarize.md +22 -0
package/templates/command-archive/docs/update.md +76 -0
package/templates/command-archive/journal.md +18 -0
package/templates/{commands → command-archive}/kanban.md +5 -7
package/templates/{commands → command-archive}/plan/archive.md +2 -2
package/templates/command-archive/plan/red-team.md +200 -0
package/templates/command-archive/plan/validate.md +188 -0
package/templates/command-archive/preview.md +283 -0
package/templates/command-archive/review/codebase/parallel.md +122 -0
package/templates/{commands → command-archive}/test/ui.md +3 -3
package/templates/{commands → command-archive}/use-mcp.md +6 -2
package/templates/command-archive/worktree.md +109 -0
package/templates/{workflows → rules}/development-rules.md +12 -53
package/templates/rules/orchestration-protocol.md +43 -0
package/templates/{workflows → rules}/primary-workflow.md +16 -4
package/templates/rules/team-coordination-rules.md +90 -0
package/templates/schemas/ck-config.schema.json +381 -0
package/templates/commands/README.md +0 -251
package/templates/commands/bootstrap/auto/fast.md +0 -111
package/templates/commands/bootstrap/auto/parallel.md +0 -66
package/templates/commands/bootstrap/auto.md +0 -115
package/templates/commands/bootstrap.md +0 -137
package/templates/commands/brainstorm.md +0 -74
package/templates/commands/build.md +0 -39
package/templates/commands/checkpoint.md +0 -156
package/templates/commands/code/auto.md +0 -170
package/templates/commands/code/no-test.md +0 -158
package/templates/commands/code/parallel.md +0 -55
package/templates/commands/code-simplifier.md +0 -71
package/templates/commands/code.md +0 -176
package/templates/commands/compact.md +0 -57
package/templates/commands/content/cro.md +0 -43
package/templates/commands/content/enhance.md +0 -14
package/templates/commands/content/fast.md +0 -13
package/templates/commands/content/good.md +0 -16
package/templates/commands/context.md +0 -48
package/templates/commands/cook/auto/fast.md +0 -26
package/templates/commands/cook/auto/parallel.md +0 -49
package/templates/commands/cook/auto.md +0 -15
package/templates/commands/cook/fast.md +0 -47
package/templates/commands/cook/hard.md +0 -80
package/templates/commands/cook/parallel.md +0 -90
package/templates/commands/cook.md +0 -105
package/templates/commands/create-feature.md +0 -48
package/templates/commands/db-migrate.md +0 -52
package/templates/commands/debug.md +0 -13
package/templates/commands/design/3d.md +0 -83
package/templates/commands/design/describe.md +0 -23
package/templates/commands/design/fast.md +0 -31
package/templates/commands/design/good.md +0 -35
package/templates/commands/design/screenshot.md +0 -34
package/templates/commands/design/video.md +0 -34
package/templates/commands/docs/init.md +0 -39
package/templates/commands/docs/summarize.md +0 -31
package/templates/commands/docs/update.md +0 -57
package/templates/commands/feature.md +0 -62
package/templates/commands/fix/ci.md +0 -17
package/templates/commands/fix/fast.md +0 -19
package/templates/commands/fix/hard.md +0 -39
package/templates/commands/fix/logs.md +0 -26
package/templates/commands/fix/parallel.md +0 -54
package/templates/commands/fix/test.md +0 -20
package/templates/commands/fix/types.md +0 -9
package/templates/commands/fix/ui.md +0 -48
package/templates/commands/fix-issue.md +0 -177
package/templates/commands/fix.md +0 -43
package/templates/commands/generate-dto.md +0 -67
package/templates/commands/git/cm.md +0 -5
package/templates/commands/git/cp.md +0 -4
package/templates/commands/git/merge.md +0 -40
package/templates/commands/git/pr.md +0 -48
package/templates/commands/integrate/polar.md +0 -28
package/templates/commands/integrate/sepay.md +0 -28
package/templates/commands/investigate.md +0 -324
package/templates/commands/journal.md +0 -7
package/templates/commands/lint.md +0 -47
package/templates/commands/migration.md +0 -111
package/templates/commands/performance.md +0 -110
package/templates/commands/plan/ci.md +0 -33
package/templates/commands/plan/cro.md +0 -69
package/templates/commands/plan/fast.md +0 -86
package/templates/commands/plan/hard.md +0 -103
package/templates/commands/plan/parallel.md +0 -152
package/templates/commands/plan/preview.md +0 -40
package/templates/commands/plan/two.md +0 -52
package/templates/commands/plan/validate.md +0 -132
package/templates/commands/plan.md +0 -36
package/templates/commands/pr.md +0 -49
package/templates/commands/preview.md +0 -87
package/templates/commands/release-notes.md +0 -144
package/templates/commands/review/post-task.md +0 -157
package/templates/commands/review-changes.md +0 -46
package/templates/commands/review.md +0 -56
package/templates/commands/scout/ext.md +0 -35
package/templates/commands/scout.md +0 -283
package/templates/commands/security.md +0 -119
package/templates/commands/skill/add.md +0 -36
package/templates/commands/skill/create.md +0 -29
package/templates/commands/skill/fix-logs.md +0 -22
package/templates/commands/skill/optimize/auto.md +0 -25
package/templates/commands/skill/optimize.md +0 -34
package/templates/commands/skill/plan.md +0 -45
package/templates/commands/worktree.md +0 -126
package/templates/memory/session-log.md +0 -186
package/templates/router/README.md +0 -294
package/templates/router/agents-guide.md +0 -38
package/templates/router/commands-guide.md +0 -122
package/templates/router/decision-flow.md +0 -92
package/templates/router/skills-guide.md +0 -127
package/templates/router/workflows-guide.md +0 -68
package/templates/workflows/README.md +0 -241
package/templates/workflows/orchestration-protocol.md +0 -16
/package/templates/{commands → command-archive}/coding-level.md +0 -0
/package/templates/{commands → command-archive}/review/codebase.md +0 -0
/package/templates/{commands → command-archive}/test.md +0 -0
/package/templates/{commands → command-archive}/watzup.md +0 -0
/package/templates/{workflows → rules}/documentation-management.md +0 -0

package/templates/commands/preview.md DELETED Viewed

@@ -1,87 +0,0 @@
----
-description: Path to markdown file, plan directory, or plans collection
-arguments:
-  - name: path
-    description: Path to file or directory to preview
-    required: false
----
-Universal viewer using `markdown-novel-viewer` skill - pass ANY path and see it rendered nicely.
-## Usage
-- `/preview <file.md>` - View markdown file in novel-reader UI
-- `/preview <directory/>` - Browse directory contents
-- `/preview --stop` - Stop running server
-## Examples
-```bash
-/preview plans/my-plan/plan.md     # View markdown file
-/preview plans/                    # Browse plans directory
-/preview docs/                     # Browse docs directory
-/preview any/path/to/file.md      # View any markdown file
-/preview any/path/                 # Browse any directory
-```
-## Execution
-**IMPORTANT:** Run server as Claude Code background task using `run_in_background: true` with the Bash tool. This makes the server visible in `/tasks` and manageable via `KillShell`.
-Check if this script is located in the current workspace or in `$HOME/.claude/skills/markdown-novel-viewer` directory:
-- If in current workspace: `$SKILL_DIR_PATH` = `./.claude/skills/markdown-novel-viewer/`
-- If in home directory: `$SKILL_DIR_PATH` = `$HOME/.claude/skills/markdown-novel-viewer/`
-### Stop Server
-If `--stop` flag is provided:
-```bash
-node $SKILL_DIR_PATH/scripts/server.cjs --stop
-```
-### Start Server
-Otherwise, run the `markdown-novel-viewer` server as CC background task with `--foreground` flag (keeps process alive for CC task management):
-```bash
-# Determine if path is file or directory
-INPUT_PATH="{{path}}"
-if [[ -d "$INPUT_PATH" ]]; then
-  # Directory mode - browse
-  node $SKILL_DIR_PATH/scripts/server.cjs \
-    --dir "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-else
-  # File mode - view markdown
-  node $SKILL_DIR_PATH/scripts/server.cjs \
-    --file "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-fi
-```
-**Critical:** When calling the Bash tool:
-- Set `run_in_background: true` to run as CC background task
-- Set `timeout: 300000` (5 minutes) to prevent premature termination
-- Parse JSON output and report URL to user
-Example Bash tool call:
-```json
-{
-  "command": "node .claude/skills/markdown-novel-viewer/scripts/server.cjs --dir \"path\" --host 0.0.0.0 --open --foreground",
-  "run_in_background": true,
-  "timeout": 300000,
-  "description": "Start preview server in background"
-}
-```
-After starting, parse the JSON output (e.g., `{"success":true,"url":"http://localhost:3456/view?file=...","networkUrl":"http://192.168.1.x:3456/view?file=..."}`) and report:
-- Local URL for browser access
-- Network URL for remote device access (if available)
-- Inform user that server is now running as CC background task (visible in `/tasks`)
-**CRITICAL:** MUST display the FULL URL including path and query string (e.g., `http://localhost:3456/view?file=/path/to/file.md`). NEVER truncate to just `host:port` (e.g., `http://localhost:3456`). The full URL is required for direct file access.

package/templates/commands/release-notes.md DELETED Viewed

@@ -1,144 +0,0 @@
-# Generate Release Notes: $ARGUMENTS
-Generate or update release notes for a feature or PR.
-## Phase 1: Determine Source
-Parse input from: $ARGUMENTS
-**Source Options:**
-1. `--source=<path>` - Use feature documentation file
-2. `--compare=<base>:<head>` - Compare git branches
-3. `--investigate` - Manual investigation mode
-If no option specified, prompt for source.
-## Phase 2: Gather Information
-### Option A: From Feature Documentation
-```bash
-# Read the feature documentation
-cat <source-path>
-```
-Extract:
-- Feature name and description
-- Key capabilities
-- Technical implementation
-- API endpoints
-- UI components
-### Option B: From Branch Comparison
-```bash
-# Fetch latest
-git fetch origin
-# Get commits between branches
-git log origin/<base>...origin/<head> --oneline
-# Get file changes
-git diff origin/<base>...origin/<head> --stat
-# Get detailed diff
-git diff origin/<base>...origin/<head>
-```
-Extract:
-- Changed files
-- New features
-- Bug fixes
-- Breaking changes
-### Option C: Investigation Mode
-1. Ask user for feature scope
-2. Search codebase for relevant files
-3. Analyze implementation
-## Phase 3: Generate Release Note
-Create file at: `docs/release-notes/YYMMDD-<feature-slug>.md`
-**Filename Format:**
-- YY = 2-digit year
-- MM = 2-digit month
-- DD = 2-digit day
-- feature-slug = kebab-case feature name
-**Template:**
-```markdown
-# Release Notes: [Feature Name]
-**Date:** YYYY-MM-DD
-**Version:** X.Y.Z (if applicable)
-**Status:** Draft | Released
----
-## Summary
-[One paragraph describing the feature and its value to users]
-## New Features
-- **[Feature 1]**: Brief description
-- **[Feature 2]**: Brief description
-## Improvements
-- **[Improvement 1]**: Brief description
-## Bug Fixes
-- **[Fix 1]**: Brief description
-## Breaking Changes
-> **Warning**: Breaking changes require migration
-- [Breaking change description and migration path]
-## Technical Details
-### Backend
-- [Service changes]
-- [API changes]
-### Frontend
-- [Component changes]
-- [UI changes]
-### Database
-- [Migration info]
-## Related Documentation
-- [Feature Documentation](../business-features/...)
-- [API Reference](../api/...)
-## Contributors
-- @contributor
----
-*Generated with [Claude Code](https://claude.com/claude-code)*
-```
-## Phase 4: Review & Finalize
-1. Present the generated release note
-2. Ask for any corrections or additions
-3. Save the file
-## Examples
-```bash
-# From feature docs
-/release-notes kudos --source=docs/business-features/TextSnippet/detailed-features/README.KudosFeature.md
-# From branch comparison
-/release-notes employee-export --compare=feature/employee-export:develop
-# Investigation mode
-/release-notes authentication --investigate
-```

package/templates/commands/review/post-task.md DELETED Viewed

@@ -1,157 +0,0 @@
----
-description: ⚡⚡⚡ Two-pass code review for task completion
-argument-hint: [optional-focus-area]
----
-# Post-Task Two-Pass Code Review
-Execute mandatory two-pass review protocol after completing code changes.
-Focus: $ARGUMENTS
----
-## Protocol Overview
-This review ensures ALL code changes follow best practices and project conventions.
-Two passes guarantee corrections don't introduce new issues.
----
-## Pass 1: Initial Review
-### Step 1.1: Gather Changes
-```bash
-# Get unstaged changes summary
-git diff --stat
-# Get detailed changes
-git diff
-```
-### Step 1.2: Review Checklist
-**Task Correctness:**
-- [ ] Changes achieve the intended task objective
-- [ ] No unrelated/unnecessary modifications
-- [ ] Edge cases handled appropriately
-- [ ] Error handling is complete
-**Code Standards (EasyPlatform):**
-*Backend:*
-- [ ] Uses platform repository (IPlatformQueryableRootRepository)
-- [ ] Uses PlatformValidationResult fluent API (.And(), .AndAsync())
-- [ ] Side effects in Entity Event Handlers, not command handlers
-- [ ] DTOs own mapping via MapToEntity()/MapToObject()
-- [ ] Command + Result + Handler in ONE file
-*Frontend:*
-- [ ] Extends appropriate base class (AppBaseComponent, AppBaseVmStoreComponent, AppBaseFormComponent)
-- [ ] Uses PlatformVmStore for state management
-- [ ] Uses .pipe(this.untilDestroyed()) for subscriptions
-- [ ] All template elements have BEM classes
-**Architecture:**
-- [ ] Logic placed in lowest appropriate layer (Entity > Service > Component)
-- [ ] No cross-service direct database access
-- [ ] Follows existing patterns found in codebase
-**Security:**
-- [ ] No hardcoded secrets or credentials
-- [ ] Input validation at boundaries
-- [ ] Proper authorization checks
-### Step 1.3: Execute Corrections
-If any issues found:
-1. Fix each issue directly
-2. Mark `PASS_1_MADE_CHANGES = true`
-3. Proceed to Pass 2
-If no issues found:
-1. Mark `PASS_1_MADE_CHANGES = false`
-2. Skip to Final Report
----
-## Pass 2: Re-Review (Conditional)
-**ONLY EXECUTE IF PASS 1 MADE CHANGES**
-### Step 2.1: Verify All Changes
-```bash
-# Check updated changes
-git diff --stat
-git diff
-```
-### Step 2.2: Full Re-Review
-Repeat Pass 1 checklist on ALL current changes (original + corrections).
-Focus areas:
-- [ ] Original task still correctly implemented
-- [ ] Corrections are valid and complete
-- [ ] No new issues introduced by corrections
-- [ ] Code is production-ready
-### Step 2.3: Final Corrections
-If issues found:
-- Apply minimal, targeted fixes
-- Document any trade-offs made
----
-## Final Report
-### Summary Template
-```markdown
-## Post-Task Review Complete
-**Task:** [Brief description]
-**Pass 1 Result:** [Clean / N issues fixed]
-**Pass 2 Required:** [Yes/No]
-**Pass 2 Result:** [N/A / Clean / N issues fixed]
-### Changes Summary
-- [List of files modified]
-- [Key changes made]
-### Issues Found & Fixed
-1. [Issue]: [Fix applied]
-2. ...
-### Remaining Concerns (if any)
-- [Concern]: [Reason not addressed / Recommended follow-up]
-### Verification
-- [ ] Task objective achieved
-- [ ] Code follows project conventions
-- [ ] No security vulnerabilities
-- [ ] Ready for commit
-```
----
-## Quick Commands
-```bash
-# View changes for review
-git diff --stat && git diff
-# Check specific file
-git diff path/to/file.ts
-# Discard a problematic change
-git checkout -- path/to/file.ts
-# Stage reviewed changes
-git add -p  # Interactive staging
-```
----
-## Integration Notes
-- This command is auto-triggered by workflow orchestration after `/cook`, `/fix`, `/code`
-- Can be manually invoked anytime with `/review:post-task`
-- For PR reviews, use `/review:codebase` instead
-- Use `code-reviewer` subagent for complex reviews requiring deeper analysis

package/templates/commands/review-changes.md DELETED Viewed

@@ -1,46 +0,0 @@
----
-description: Review all uncommitted changes before commit
-allowed-tools: Bash, Read, Glob, Grep, TodoWrite
----
-Review all uncommitted changes and provide feedback.
-## Steps:
-1. **Get Change Summary**
-   - Run `git status` to see all changed files
-   - Run `git diff` to see actual changes (staged and unstaged)
-2. **Analyze Each Changed File**
-   For each modified file, check:
-   - Does it follow platform patterns from CLAUDE.md?
-   - Any security concerns (hardcoded secrets, SQL injection, XSS)?
-   - Any performance issues (N+1 queries, missing async/await)?
-   - Proper error handling?
-   - Code style compliance?
-3. **Check for Common Issues**
-   - Unused imports or variables
-   - Console.log/Debug.WriteLine statements left in
-   - Hardcoded values that should be configuration
-   - Missing async/await keywords
-   - Incorrect exception handling
-   - Missing validation
-4. **Backend-Specific Checks**
-   - CQRS patterns followed correctly
-   - Repository usage (no direct DbContext access)
-   - Entity DTO mapping patterns
-   - Validation using PlatformValidationResult
-5. **Frontend-Specific Checks**
-   - Component base class inheritance correct
-   - State management patterns
-   - Memory leaks (missing unsubscribe)
-   - Template binding issues
-6. **Provide Summary**
-   - **Critical Issues**: Must fix before commit
-   - **Warnings**: Should consider fixing
-   - **Info**: Minor suggestions
-   - **Suggested commit message**: Based on changes

package/templates/commands/review.md DELETED Viewed

@@ -1,56 +0,0 @@
-# Code Review: $ARGUMENTS
-Perform a comprehensive code review following EasyPlatform standards.
-## Review Scope
-Target: $ARGUMENTS (can be a PR number, file path, or branch name)
-## Review Checklist
-### 1. Architecture Compliance
-- [ ] Follows Clean Architecture layers (Domain, Application, Persistence, Service)
-- [ ] Uses correct repository pattern (I{Service}RootRepository<T>)
-- [ ] CQRS pattern: Command/Query + Handler + Result in ONE file
-- [ ] No cross-service direct database access
-### 2. Code Quality
-- [ ] Single Responsibility Principle
-- [ ] No code duplication
-- [ ] Meaningful variable/method names
-- [ ] Appropriate error handling with PlatformValidationResult
-### 3. Platform Patterns
-- [ ] Uses platform validation fluent API (.And(), .AndAsync())
-- [ ] No direct side effects in command handlers (use entity events)
-- [ ] DTO mapping in DTO classes, not handlers
-- [ ] Static expressions for entity queries
-### 4. Security
-- [ ] No hardcoded credentials
-- [ ] Proper authorization checks
-- [ ] Input validation at boundaries
-- [ ] No SQL injection risks
-### 5. Performance
-- [ ] Parallel operations where independent
-- [ ] Proper pagination for lists
-- [ ] No N+1 query patterns
-- [ ] Appropriate use of async/await
-## Output Format
-Provide feedback in this format:
-**Summary:** Brief overall assessment
-**Critical Issues:** (Must fix)
-- Issue 1: Description and suggested fix
-- Issue 2: Description and suggested fix
-**Suggestions:** (Nice to have)
-- Suggestion 1
-- Suggestion 2
-**Positive Notes:**
-- What was done well

package/templates/commands/scout/ext.md DELETED Viewed

@@ -1,35 +0,0 @@
----
-description: ⚡ Use external agentic tools to scout given directories
-argument-hint: [user-prompt] [scale]
----
-## Purpose
-Utilize external agentic tools to scout given directories or explore the codebase for files needed to complete the task using a fast, token efficient agent.
-## Variables
-USER_PROMPT: $1
-SCALE: $2 (defaults to 3)
-RELEVANT_FILE_OUTPUT_DIR: Use `Report:` from `## Naming` section
-## Workflow:
-- Write a prompt for 'SCALE' number of agents to the `Task` tool that will immediately call the `Bash` tool to run these commands to kick off your agents to conduct the search:
-  - `gemini -p "[prompt]" --model gemini-2.5-flash-preview-09-2025` (if count <= 3)
-  - `opencode run "[prompt]" --model opencode/grok-code` (if count > 3 and count < 6)
-  - if count >= 6, spawn `Explore` subagents to search the codebase in parallel
-**Why use external agentic tools?**
-- External agentic tools are faster and more efficient when using LLMs with large context windows (1M+ tokens).
-**How to prompt the agents:**
-- If `gemini` or `opencode` is not available, ask the user if they want to install it:
-  - If **yes**, install it (if there are permission issues, instruct the user to install it manually, including authentication steps)
-  - If **no**, use the default `Explore` subagents.
-- IMPORTANT: Kick these agents off in parallel using the `Task` tool, analyze and divide folders for each agent to scout intelligently and quickly.
-- IMPORTANT: These agents are calling OTHER agentic coding tools to search the codebase. DO NOT call any search tools yourself.
-- IMPORTANT: That means with the `Task` tool, you'll immediately call the Bash tool to run the respective agentic coding tool (gemini, opencode, claude, etc.)
-- IMPORTANT: Instruct the agents to quickly search the codebase for files needed to complete the task. This isn't about a full blown search, just a quick search to find the files needed to complete the task.
-- Instruct the subagent to use a timeout of 3 minutes for each agent's bash call. Skip any agents that don't return within the timeout, don't restart them.
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.