@amrhas82/agentic-kit 1.7.5 → 1.7.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amrhas82/agentic-kit",
-  "version": "1.7.5",
+  "version": "1.7.6",
   "description": "Comprehensive toolkit for AI-driven software development with 13 specialized agents and 22 powerful skills. Interactive multi-tool installer supports Claude, Opencode, Ampcode, and Droid. Available in 3 variants: Lite (3 agents, 510 KB), Standard (13 agents, 8 skills, 8.4 MB), Pro (13 agents, 22 skills, 9 MB)",
   "main": "index.js",
   "bin": {

package/packages/ampcode/commands/brainstorming.md

@@ -1,5 +1,4 @@
 ---
-id: brainstorming
 name: brainstorming
 description: Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
 usage: /brainstorming <session-type> <topic>

package/packages/ampcode/commands/code-review.md

@@ -1,5 +1,4 @@
 ---
-id: code-review
 name: code-review
 description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements - reviews implementation against plan or requirements before proceeding
 usage: /code-review <review-scope> <focus-areas>

package/packages/ampcode/commands/condition-based-waiting.md

@@ -1,5 +1,4 @@
 ---
-id: condition-based-waiting
 name: condition-based-waiting
 description: Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
 usage: /condition-based-waiting <condition-type> <timeout-specs>

package/packages/ampcode/commands/debug.md

@@ -1,5 +1,4 @@
 ---
-id: debug
 name: debug
 description: Debug issue [issue]
 usage: /debug <issue-description>

package/packages/ampcode/commands/docs-builder.md

@@ -1,5 +1,4 @@
 ---
-id: docs-builder
 name: docs-builder
 description: Create comprehensive project documentation with structured /docs hierarchy
 usage: /docs-builder

package/packages/ampcode/commands/explain.md

@@ -1,5 +1,4 @@
 ---
-id: explain
 name: explain
 description: Explain [code]
 usage: /explain <code-section>

package/packages/ampcode/commands/git-commit.md

@@ -1,5 +1,4 @@
 ---
-id: git-commit
 name: git-commit
 description: Analyze changes and commit
 usage: /git-commit

package/packages/ampcode/commands/optimize.md

@@ -1,5 +1,4 @@
 ---
-id: optimize
 name: optimize
 description: Optimize performance [target]
 usage: /optimize <target-area>

package/packages/ampcode/commands/refactor.md

@@ -1,5 +1,4 @@
 ---
-id: refactor
 name: refactor
 description: Refactor [code]
 usage: /refactor <code-section>

package/packages/ampcode/commands/review.md

@@ -1,5 +1,4 @@
 ---
-id: review
 name: review
 description: Review code [file]
 usage: /review

package/packages/ampcode/commands/root-cause-tracing.md

@@ -1,5 +1,4 @@
 ---
-id: root-cause-tracing
 name: root-cause-tracing
 description: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
 usage: /root-cause-tracing <issue-description>

package/packages/ampcode/commands/security.md

@@ -1,5 +1,4 @@
 ---
-id: security
 name: security
 description: Scan security [target]
 usage: /security

package/packages/ampcode/commands/ship.md

@@ -1,5 +1,4 @@
 ---
-id: ship
 name: ship
 description: Check pre-deployment
 usage: /ship

package/packages/ampcode/commands/skill-creator.md

@@ -1,5 +1,4 @@
 ---
-id: skill-creator
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 usage: /skill-creator <skill-type> <skill-description>

package/packages/ampcode/commands/subagent-spawning.md

@@ -1,5 +1,4 @@
 ---
-id: subagent-spawning
 name: subagent-spawning
 description: Use when spawning fresh subagents for isolated task execution. Provides TDD-aware templates for 3-process-task-list and other agents.
 usage: Used by 3-process-task-list and other agents for clean subagent execution

package/packages/ampcode/commands/systematic-debugging.md

@@ -1,5 +1,4 @@
 ---
-id: systematic-debugging
 name: systematic-debugging
 description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
 usage: /systematic-debugging <bug-or-error-description>

package/packages/ampcode/commands/test-generate.md

@@ -1,5 +1,4 @@
 ---
-id: test-generate
 name: test-generate
 description: Generate tests [file]
 usage: /test-generate <code-section>

package/packages/ampcode/commands/testing-anti-patterns.md

@@ -1,5 +1,4 @@
 ---
-id: testing-anti-patterns
 name: testing-anti-patterns
 description: Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
 usage: /testing-anti-patterns <testing-scenario>

package/packages/ampcode/commands/verification-before-completion.md

@@ -1,5 +1,4 @@
 ---
-id: verification-before-completion
 name: verification-before-completion
 description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
 usage: /verification-before-completion <work-to-verify>

package/packages/claude/commands/debug.md

@@ -1,5 +1,4 @@
 ---
-id: debug
 name: debug
 description: Debug issue [issue]
 usage: /debug <issue-description>

package/packages/claude/commands/explain.md

@@ -1,5 +1,4 @@
 ---
-id: explain
 name: explain
 description: Explain [code]
 usage: /explain <code-section>

package/packages/claude/commands/git-commit.md

@@ -1,5 +1,4 @@
 ---
-id: git-commit
 name: git-commit
 description: Analyze changes and commit
 usage: /git-commit

package/packages/claude/commands/optimize.md

@@ -1,5 +1,4 @@
 ---
-id: optimize
 name: optimize
 description: Optimize performance [target]
 usage: /optimize <target-area>

package/packages/claude/commands/refactor.md

@@ -1,5 +1,4 @@
 ---
-id: refactor
 name: refactor
 description: Refactor [code]
 usage: /refactor <code-section>

package/packages/claude/commands/review.md

@@ -1,5 +1,4 @@
 ---
-id: review
 name: review
 description: Review code [file]
 usage: /review

package/packages/claude/commands/security.md

@@ -1,5 +1,4 @@
 ---
-id: security
 name: security
 description: Scan security [target]
 usage: /security

package/packages/claude/commands/ship.md

@@ -1,5 +1,4 @@
 ---
-id: ship
 name: ship
 description: Check pre-deployment
 usage: /ship

package/packages/claude/commands/test-generate.md

@@ -1,5 +1,4 @@
 ---
-id: test-generate
 name: test-generate
 description: Generate tests [file]
 usage: /test-generate <code-section>

package/packages/claude/skills/brainstorming/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: brainstorming
 name: brainstorming
 description: Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
 usage: /brainstorming <session-type> <topic>

package/packages/claude/skills/code-review/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: code-review
 name: code-review
 description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements - reviews implementation against plan or requirements before proceeding
 usage: /code-review <review-scope> <focus-areas>

package/packages/claude/skills/condition-based-waiting/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: condition-based-waiting
 name: condition-based-waiting
 description: Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
 usage: /condition-based-waiting <condition-type> <timeout-specs>

package/packages/claude/skills/docs-builder/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: docs-builder
 name: docs-builder
 description: Create comprehensive project documentation with structured /docs hierarchy
 usage: /docs-builder

package/packages/claude/skills/root-cause-tracing/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: root-cause-tracing
 name: root-cause-tracing
 description: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
 usage: /root-cause-tracing <issue-description>

package/packages/claude/skills/skill-creator/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: skill-creator
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 usage: /skill-creator <skill-type> <skill-description>

package/packages/claude/skills/subagent-spawning/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: subagent-spawning
 name: subagent-spawning
 description: Use when spawning fresh subagents for isolated task execution. Provides TDD-aware templates for 3-process-task-list and other agents.
 usage: Used by 3-process-task-list and other agents for clean subagent execution

package/packages/claude/skills/systematic-debugging/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: systematic-debugging
 name: systematic-debugging
 description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
 usage: /systematic-debugging <bug-or-error-description>

package/packages/claude/skills/test-driven-development/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: test-driven-development
 name: test-driven-development
 description: Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
 usage: /test-driven-development <feature-or-behavior-to-test>

package/packages/claude/skills/testing-anti-patterns/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: testing-anti-patterns
 name: testing-anti-patterns
 description: Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
 usage: /testing-anti-patterns <testing-scenario>

package/packages/claude/skills/verification-before-completion/SKILL.md

@@ -1,5 +1,4 @@
 ---
-id: verification-before-completion
 name: verification-before-completion
 description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
 usage: /verification-before-completion <work-to-verify>

package/packages/droid/commands/brainstorming.md

@@ -1,5 +1,4 @@
 ---
-id: brainstorming
 name: brainstorming
 description: Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
 usage: /brainstorming <session-type> <topic>

package/packages/droid/commands/code-review.md

@@ -1,5 +1,4 @@
 ---
-id: code-review
 name: code-review
 description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements - reviews implementation against plan or requirements before proceeding
 usage: /code-review <review-scope> <focus-areas>

package/packages/droid/commands/condition-based-waiting.md

@@ -1,5 +1,4 @@
 ---
-id: condition-based-waiting
 name: condition-based-waiting
 description: Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
 usage: /condition-based-waiting <condition-type> <timeout-specs>

package/packages/droid/commands/debug.md

@@ -1,5 +1,4 @@
 ---
-id: debug
 name: debug
 description: Debug issue [issue]
 usage: /debug <issue-description>

package/packages/droid/commands/docs-builder.md

@@ -1,5 +1,4 @@
 ---
-id: docs-builder
 name: docs-builder
 description: Create comprehensive project documentation with structured /docs hierarchy
 usage: /docs-builder

package/packages/droid/commands/explain.md

@@ -1,5 +1,4 @@
 ---
-id: explain
 name: explain
 description: Explain [code]
 usage: /explain <code-section>

package/packages/droid/commands/git-commit.md

@@ -1,5 +1,4 @@
 ---
-id: git-commit
 name: git-commit
 description: Analyze changes and commit
 usage: /git-commit

package/packages/droid/commands/optimize.md

@@ -1,5 +1,4 @@
 ---
-id: optimize
 name: optimize
 description: Optimize performance [target]
 usage: /optimize <target-area>

package/packages/droid/commands/refactor.md

@@ -1,5 +1,4 @@
 ---
-id: refactor
 name: refactor
 description: Refactor [code]
 usage: /refactor <code-section>

package/packages/droid/commands/review.md

@@ -1,5 +1,4 @@
 ---
-id: review
 name: review
 description: Review code [file]
 usage: /review

package/packages/droid/commands/root-cause-tracing.md

@@ -1,5 +1,4 @@
 ---
-id: root-cause-tracing
 name: root-cause-tracing
 description: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
 usage: /root-cause-tracing <issue-description>

package/packages/droid/commands/security.md

@@ -1,5 +1,4 @@
 ---
-id: security
 name: security
 description: Scan security [target]
 usage: /security

package/packages/droid/commands/ship.md

@@ -1,5 +1,4 @@
 ---
-id: ship
 name: ship
 description: Check pre-deployment
 usage: /ship

package/packages/droid/commands/skill-creator.md

@@ -1,5 +1,4 @@
 ---
-id: skill-creator
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 usage: /skill-creator <skill-type> <skill-description>

package/packages/droid/commands/subagent-spawning.md

@@ -1,5 +1,4 @@
 ---
-id: subagent-spawning
 name: subagent-spawning
 description: Use when spawning fresh subagents for isolated task execution. Provides TDD-aware templates for 3-process-task-list and other agents.
 usage: Used by 3-process-task-list and other agents for clean subagent execution

package/packages/droid/commands/systematic-debugging.md

@@ -1,5 +1,4 @@
 ---
-id: systematic-debugging
 name: systematic-debugging
 description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
 usage: /systematic-debugging <bug-or-error-description>

package/packages/droid/commands/test-generate.md

@@ -1,5 +1,4 @@
 ---
-id: test-generate
 name: test-generate
 description: Generate tests [file]
 usage: /test-generate <code-section>

package/packages/droid/commands/testing-anti-patterns.md

@@ -1,5 +1,4 @@
 ---
-id: testing-anti-patterns
 name: testing-anti-patterns
 description: Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
 usage: /testing-anti-patterns <testing-scenario>

package/packages/droid/commands/verification-before-completion.md

@@ -1,5 +1,4 @@
 ---
-id: verification-before-completion
 name: verification-before-completion
 description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
 usage: /verification-before-completion <work-to-verify>

package/packages/opencode/command/brainstorming.md

@@ -1,5 +1,4 @@
 ---
-id: brainstorming
 name: brainstorming
 description: Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
 usage: /brainstorming <session-type> <topic>

package/packages/opencode/command/code-review.md

@@ -1,5 +1,4 @@
 ---
-id: code-review
 name: code-review
 description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements - reviews implementation against plan or requirements before proceeding
 usage: /code-review <review-scope> <focus-areas>

package/packages/opencode/command/condition-based-waiting.md

@@ -1,5 +1,4 @@
 ---
-id: condition-based-waiting
 name: condition-based-waiting
 description: Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
 usage: /condition-based-waiting <condition-type> <timeout-specs>

package/packages/opencode/command/debug.md

@@ -1,5 +1,4 @@
 ---
-id: debug
 name: debug
 description: Debug issue [issue]
 usage: /debug <issue-description>

package/packages/opencode/command/docs-builder.md

@@ -1,5 +1,4 @@
 ---
-id: docs-builder
 name: docs-builder
 description: Create comprehensive project documentation with structured /docs hierarchy
 usage: /docs-builder

package/packages/opencode/command/explain.md

@@ -1,5 +1,4 @@
 ---
-id: explain
 name: explain
 description: Explain [code]
 usage: /explain <code-section>

package/packages/opencode/command/git-commit.md

@@ -1,5 +1,4 @@
 ---
-id: git-commit
 name: git-commit
 description: Analyze changes and commit
 usage: /git-commit

package/packages/opencode/command/optimize.md

@@ -1,5 +1,4 @@
 ---
-id: optimize
 name: optimize
 description: Optimize performance [target]
 usage: /optimize <target-area>

package/packages/opencode/command/refactor.md

@@ -1,5 +1,4 @@
 ---
-id: refactor
 name: refactor
 description: Refactor [code]
 usage: /refactor <code-section>

package/packages/opencode/command/review.md

@@ -1,5 +1,4 @@
 ---
-id: review
 name: review
 description: Review code [file]
 usage: /review

package/packages/opencode/command/root-cause-tracing.md

@@ -1,5 +1,4 @@
 ---
-id: root-cause-tracing
 name: root-cause-tracing
 description: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
 usage: /root-cause-tracing <issue-description>

package/packages/opencode/command/security.md

@@ -1,5 +1,4 @@
 ---
-id: security
 name: security
 description: Scan security [target]
 usage: /security

package/packages/opencode/command/ship.md

@@ -1,5 +1,4 @@
 ---
-id: ship
 name: ship
 description: Check pre-deployment
 usage: /ship

package/packages/opencode/command/skill-creator.md

@@ -1,5 +1,4 @@
 ---
-id: skill-creator
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 usage: /skill-creator <skill-type> <skill-description>

package/packages/opencode/command/subagent-spawning.md

@@ -1,5 +1,4 @@
 ---
-id: subagent-spawning
 name: subagent-spawning
 description: Use when spawning fresh subagents for isolated task execution. Provides TDD-aware templates for 3-process-task-list and other agents.
 usage: Used by 3-process-task-list and other agents for clean subagent execution

package/packages/opencode/command/systematic-debugging.md

@@ -1,5 +1,4 @@
 ---
-id: systematic-debugging
 name: systematic-debugging
 description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
 usage: /systematic-debugging <bug-or-error-description>

package/packages/opencode/command/test-generate.md

@@ -1,5 +1,4 @@
 ---
-id: test-generate
 name: test-generate
 description: Generate tests [file]
 usage: /test-generate <code-section>

package/packages/opencode/command/testing-anti-patterns.md

@@ -1,5 +1,4 @@
 ---
-id: testing-anti-patterns
 name: testing-anti-patterns
 description: Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
 usage: /testing-anti-patterns <testing-scenario>

package/packages/opencode/command/verification-before-completion.md

@@ -1,5 +1,4 @@
 ---
-id: verification-before-completion
 name: verification-before-completion
 description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
 usage: /verification-before-completion <work-to-verify>