@tdsoft-tech/aikit 0.1.14 → 0.1.15

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## [0.1.15] - 2026-01-01
+
+### Breaking Changes ⚠️
+- 🏷️ **Command & Skill Prefix Separation** - All OpenCode commands now use prefixes to distinguish type:
+  - Commands: `/ak_cm_<name>` (e.g., `/ak_cm_plan`, `/ak_cm_implement`, `/ak_cm_fix`)
+  - Skills: `/ak_sk_<name>` (e.g., `/ak_sk_test-driven-development`, `/ak_sk_code-review`)
+  - Old simple names (e.g., `/plan`, `/test-driven-development`) are **no longer supported**
+  - Users must press `/` in OpenCode to see new prefixed commands
+  - All documentation updated with new command names
+
+### Added
+- Clear visual distinction between commands and skills in OpenCode command picker
+- New naming convention: `ak_cm_*` for commands, `ak_sk_*` for skills
+- Updated all 28 commands and 23 skills with new prefixes
+
+### Migration Guide
+1. Run `aikit install` to generate new prefixed commands
+2. Press `/` in OpenCode to see new command structure
+3. Use `/ak_cm_` prefix for all slash commands
+4. Use `/ak_sk_` prefix for direct skill invocation
+
 ## [0.1.12] - 2024-12-28
 
 ### Added

package/dist/cli.js

@@ -2360,6 +2360,11 @@ var DEFAULT_COMMANDS = [
     content: `Create a new task in the Beads system (.beads/ directory).
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description with this command. Use it directly - do NOT ask the user for a task description!
+- The arguments contain the task description you should create
+
 1. Create a new bead file with unique ID
 2. Add task description, status, and notes
 3. Set status to "in-progress"
@@ -2379,6 +2384,11 @@ var DEFAULT_COMMANDS = [
     content: `Create a comprehensive plan before implementation.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature or task to plan. Use it directly - do NOT ask the user what to plan!
+- The arguments contain the feature/task description you should create a plan for
+
 1. UNDERSTAND: Clarify requirements through Socratic questioning
 2. RESEARCH: Check existing patterns and dependencies
 3. BREAK DOWN: Create 2-5 minute sub-tasks with:
@@ -2418,6 +2428,11 @@ Brief description of the goal.
     content: `Implement a task following TDD principles.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task reference or description. Use it directly - do NOT ask the user which task to implement!
+- The arguments contain the task reference (e.g., task-001) or task description to implement
+
 1. LOAD: Get task details from .beads/ or plan
 2. TEST: Write failing tests first (RED)
 3. IMPLEMENT: Write minimal code to pass (GREEN)
@@ -2515,6 +2530,10 @@ Before marking complete:
 
 ## Workflow
 
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description. Use it directly - do NOT ask the user what task to perform!
+- The arguments contain the task description to execute
+
 **Phase 1: Requirements Gathering**
 - Interactive selection of task type (Feature, Bug Fix, Refactoring, etc.)
 - Scope clarification
@@ -2602,7 +2621,12 @@ Before marking complete:
     content: `Quick fix with minimal ceremony.
 
 ## Workflow
-1. Identify the issue
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the issue description. Use it directly - do NOT ask user what to fix!
+- The arguments contain the issue description you should fix
+
+1. Identify issue
 2. Make minimal change to fix
 3. Verify fix works
 4. Run affected tests`
@@ -2616,6 +2640,12 @@ Before marking complete:
     content: `Fix TypeScript type errors systematically.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file argument. Use it if provided!
+- If a file argument is provided, focus on fixing types in that specific file
+- If no file argument is provided, fix all type errors in the project
+
 1. Run \`npm run typecheck\`
 2. Parse error output
 3. Fix each error in dependency order
@@ -2648,6 +2678,12 @@ Before marking complete:
     content: `Create a conventional commit.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a commit message. Use it if provided!
+- If a commit message is provided, use that message directly
+- If no message is provided, generate a conventional commit message based on changes
+
 1. Stage changes: \`git add -A\`
 2. Generate commit message following conventional commits:
    - feat: New feature
@@ -2667,6 +2703,12 @@ Before marking complete:
     content: `Create a pull request with proper description.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a PR title. Use it if provided!
+- If a title is provided, use that as the PR title
+- If no title is provided, generate a title based on changes
+
 1. Push current branch
 2. Generate PR description:
    - Summary of changes
@@ -2685,6 +2727,11 @@ Before marking complete:
     content: `Conduct thorough research and document findings.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the research topic. Use it directly - do NOT ask user what to research!
+- The arguments contain the topic you should research
+
 1. Search documentation and resources
 2. Find code examples and patterns
 3. Evaluate options and trade-offs
@@ -2722,6 +2769,12 @@ Before marking complete:
     content: `Review codebase for quality issues.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a path. Use it if provided!
+- If a path is provided, review code in that specific directory
+- If no path is provided, review the entire codebase
+
 1. Check code quality metrics
 2. Identify:
    - Code smells
@@ -2741,6 +2794,11 @@ Before marking complete:
     content: `Design a feature with thorough planning.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature to design. Use it directly - do NOT ask user what to design!
+- The arguments contain the feature you should design
+
 1. Requirements gathering (Socratic questioning)
 2. Research existing solutions
 3. Design options with trade-offs
@@ -2762,7 +2820,12 @@ Before marking complete:
     content: `Collaborative brainstorming session.
 
 ## Workflow
-1. Define the problem clearly
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided a problem. Use it directly - do NOT ask the user what to brainstorm about!
+- The arguments contain the problem you should brainstorm ideas for
+
+1. Define problem clearly
 2. Generate diverse ideas (no judgement)
 3. Group related ideas
 4. Evaluate feasibility
@@ -2778,6 +2841,11 @@ Before marking complete:
     content: `Create and switch to a new branch.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the branch name. Use it directly - do NOT ask user what to name the branch!
+- The arguments contain the branch name to create
+
 1. Ensure clean working directory
 2. Pull latest main/master
 3. Create branch with naming convention:
@@ -2796,6 +2864,12 @@ Before marking complete:
     content: `Merge current branch to target.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a target branch. Use it if provided!
+- If a target branch is provided, merge to that branch
+- If no target is provided, default to merging to main/master
+
 1. Run quality gates first
 2. Commit any pending changes
 3. Switch to target branch
@@ -2986,6 +3060,12 @@ The analysis will be saved automatically for later reference.`
     content: `Refactor code following best practices.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file or pattern argument. Use it if provided!
+- If a file/pattern argument is provided, focus refactoring on that specific target
+- If no argument is provided, identify refactoring opportunities across the codebase
+
 1. Ensure tests are in place
 2. Identify refactoring opportunities
 3. Apply refactoring incrementally
@@ -3001,6 +3081,12 @@ The analysis will be saved automatically for later reference.`
     content: `Run test suite and display results.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional pattern argument. Use it if provided!
+- If a pattern argument is provided, run tests matching that pattern
+- If no argument is provided, run the full test suite
+
 1. Run test command: \`npm run test\`
 2. Parse and display results
 3. Show coverage if available
@@ -3016,6 +3102,12 @@ The analysis will be saved automatically for later reference.`
     content: `Run linter and optionally fix issues.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided --fix flag. Check for it!
+- If --fix flag is provided, automatically fix issues
+- If no --fix flag is provided, only report issues without fixing
+
 1. Run linter: \`npm run lint\`
 2. Parse errors and warnings
 3. If --fix flag, run auto-fix
@@ -3031,6 +3123,12 @@ The analysis will be saved automatically for later reference.`
     content: `Deploy application with quality checks.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided an environment. Use it if provided!
+- If an environment is provided, deploy to that environment
+- If no environment is provided, default to production or prompt user
+
 1. Run quality gates (test, lint, build)
 2. Check for uncommitted changes
 3. Build production bundle
@@ -3046,6 +3144,12 @@ The analysis will be saved automatically for later reference.`
     content: `Rollback to previous version.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a version. Use it if provided!
+- If a version is provided, rollback to that specific version
+- If no version is provided, list available versions and prompt user
+
 1. Identify current version
 2. List available versions
 3. Confirm rollback target
@@ -3061,6 +3165,13 @@ The analysis will be saved automatically for later reference.`
     content: `View and filter application logs.
 
 ## Workflow
+
+**Step 0: Use Provided Arguments**
+IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided flags. Check for them!
+- If --tail N is provided, show only the last N lines
+- If --follow is provided, stream live log updates
+- If no flags are provided, show standard log output
+
 1. Determine log location
 2. Apply filters if specified
 3. Display logs
@@ -3165,8 +3276,8 @@ Describe what this command does.
   /**
    * Format command for agent consumption
    */
-  formatForAgent(command) {
-    return `# Command: /${command.name}
+  formatForAgent(command, args) {
+    let output = `# Command: /${command.name}
 
 ## Usage
 \`${command.usage}\`
@@ -3180,6 +3291,15 @@ ${command.examples.map((e) => `- \`${e}\``).join("\n")}
 ## Workflow
 ${command.content}
 `;
+    if (args && args.trim()) {
+      output += `
+## Arguments Provided
+\`${args}\`
+
+**IMPORTANT**: The user provided these arguments with the command. Use them in the workflow as needed.
+`;
+    }
+    return output;
   }
   /**
    * Load commands from directory (recursively)
@@ -5083,8 +5203,8 @@ async function installToOpenCode(_opencodePath) {
   const skills = await skillEngine.listSkills();
   const commands = await commandRunner.listCommands();
   const opencodeCommands = {};
-  const skillsList = skills.map((s) => `| \`/${s.name.replace(/\s+/g, "-")}\` | ${s.description} |`).join("\n");
-  opencodeCommands["skills"] = `List all available AIKit skills and how to use them.
+  const skillsList = skills.map((s) => `| \`/ak_sk_${s.name.replace(/\s+/g, "-")}\` | ${s.description} |`).join("\n");
+  opencodeCommands["ak_cm_skills"] = `List all available AIKit skills and how to use them.
 
 READ .aikit/AGENTS.md
 
@@ -5094,9 +5214,9 @@ READ .aikit/AGENTS.md
 |---------|-------------|
 ${skillsList}
 
-Type any command to use that skill. For example: \`/test-driven-development\` or \`/tdd\`.`;
+Type any command to use that skill. For example: \`/ak_sk_test-driven-development\``;
   for (const skill of skills) {
-    const commandName = skill.name.replace(/\s+/g, "-").toLowerCase();
+    const commandName = `ak_sk_${skill.name.replace(/\s+/g, "-").toLowerCase()}`;
     const skillPath = skill.filePath;
     const relativePath = skillPath.startsWith(projectPath) ? skillPath.replace(projectPath, "").replace(/\\/g, "/").replace(/^\//, "") : `.aikit/skills/${skill.name.replace(/\s+/g, "-").toLowerCase()}.md`;
     const useWhen = skill.useWhen || `The user asks you to ${skill.name}`;
@@ -5118,22 +5238,46 @@ Complete the checklist at the end of the skill.`;
   }
   for (const cmd of commands) {
     if (opencodeCommands[cmd.name]) continue;
-    const commandName = cmd.name.replace(/\//g, "").replace(/\s+/g, "-");
-    const examples = cmd.examples.map((e) => `- \`${e}\``).join("\n");
+    const commandName = `ak_cm_${cmd.name.replace(/\//g, "").replace(/\s+/g, "-")}`;
+    const examples = cmd.examples.map((e) => {
+      const prefixed = e.replace(/\//g, "/ak_cm_");
+      return `- \`${prefixed}\``;
+    }).join("\n");
     if (cmd.name === "analyze-figma") {
       opencodeCommands[commandName] = generateAnalyzeFigmaCommand();
     } else {
-      opencodeCommands[commandName] = `# Command: /${cmd.name}
+      opencodeCommands[commandName] = `# Command: /ak_cm_${cmd.name}
 
 ## Description
 ${cmd.description}
 
 ## Usage
-\`${cmd.usage}\`
+\`${cmd.usage.replace(/\//g, "/ak_cm_")}\`
 
 ## Examples
 ${examples}
 
+## \u26A0\uFE0F CRITICAL: The User Has Already Provided Arguments!
+
+**The user has provided arguments with this command!**
+
+The arguments are available in this command response - look at the command workflow below, which now includes explicit instructions to use the provided arguments.
+
+**YOUR JOB**:
+1. Follow the command workflow steps
+2. The workflow will tell you to look at "Arguments Provided" section
+3. Use those arguments - do NOT ask the user for this information!
+4. They have already provided it - extract and use it!
+
+**Example Scenario**:
+- User runs: \`/ak_cm_${cmd.name} snake game with html & css\`
+- Command: \`/ak_cm_${cmd.name}\`
+- Arguments to use: \`snake game with html & css\`
+- You must use "snake game with html & css" as provided in the workflow!
+
+**DO NOT**: Ask "Please provide a task description"
+**DO**: Follow the workflow and use the arguments provided in it!
+
 ## Workflow
 ${cmd.content}
 
@@ -5152,8 +5296,8 @@ Created ${count} OpenCode commands in .opencode/command/`);
   await configureMcpServer(projectPath);
   logger.info("\nUsage in OpenCode:");
   logger.info("  Press Ctrl+K to open command picker");
-  logger.info("  Or type /skills to see all available skills");
-  logger.info(`  Available: ${skills.length} skills, ${commands.length} commands`);
+  logger.info("  Or type /ak_cm_skills to see all available skills");
+  logger.info(`  Available: ${skills.length} skills (ak_sk_*), ${commands.length} commands (ak_cm_*)`);
   logger.info("  MCP server configured - tools available via MCP protocol");
 }
 function groupBy(array, keyFn) {