@compilr-dev/agents-coding-ts 0.1.2 → 0.1.3

package/dist/skills/code-health.js

@@ -12,6 +12,19 @@ export const codeHealthSkill = defineSkill({
     description: 'Analyze codebase health: complexity, dead code, duplicates, and anti-patterns',
     prompt: `You are in CODE HEALTH ANALYSIS mode. Analyze the codebase for quality issues.
 
+## When to Use
+- Conducting a code quality audit
+- Finding complexity hotspots before refactoring
+- Identifying dead code that can be removed
+- Detecting code duplication and anti-patterns
+- Preparing for a code review or tech debt assessment
+
+## When NOT to Use
+- Need security-focused review → use security-review skill
+- Want to understand code structure → use code-structure skill
+- Planning specific refactoring → use refactor-impact skill first
+- Checking npm package vulnerabilities → use dependency-management skill (from core)
+
 ## TOOLS TO USE
 
 1. **get_complexity**: Analyze code complexity

package/dist/skills/code-structure.js

@@ -12,6 +12,16 @@ export const codeStructureSkill = defineSkill({
     description: 'Analyze and understand codebase structure quickly',
     prompt: `You are in CODE STRUCTURE ANALYSIS mode. Analyze the specified path to understand its structure.
 
+## When to Use
+- Understanding a new file or module
+- Exploring codebase architecture
+- Finding entry points and exports
+
+## When NOT to Use
+- Need to find a specific symbol → use code-navigation skill
+- Need to refactor → use refactor-impact skill first
+- Need dependency analysis → use dependency-audit skill
+
 ## TOOLS TO USE
 
 1. **get_file_structure**: Analyze a file's internal structure

package/dist/skills/dependency-audit.js

@@ -12,6 +12,17 @@ export const dependencyAuditSkill = defineSkill({
     description: 'Audit module dependencies and identify potential issues',
     prompt: `You are in DEPENDENCY AUDIT mode. Analyze the project's module dependencies.
 
+## When to Use
+- Investigating circular dependency issues
+- Auditing module coupling before refactoring
+- Understanding dependency relationships in a codebase
+- Identifying heavy or duplicate external packages
+
+## When NOT to Use
+- Just need to understand one file's structure → use code-structure skill
+- Looking for a specific function or class → use code-navigation skill (find_symbol)
+- Checking npm package vulnerabilities → use dependency-management skill (from core)
+
 ## TOOLS TO USE
 
 1. **get_dependency_graph**: Build a complete module dependency graph

package/dist/skills/refactor-impact.js

@@ -12,6 +12,17 @@ export const refactorImpactSkill = defineSkill({
     description: 'Analyze the impact of refactoring a symbol across the codebase',
     prompt: `You are in REFACTOR IMPACT ANALYSIS mode. Analyze what would be affected by refactoring a symbol.
 
+## When to Use
+- Planning to rename, move, or change a function/class/interface
+- Assessing risk before modifying public API
+- Understanding what files will need updates
+- Creating a refactoring checklist
+
+## When NOT to Use
+- Just want to understand what a symbol does → use code-structure skill
+- Need to find where a symbol is used (not planning to change it) → use find_references directly
+- Checking type hierarchy without planning changes → use type-analysis skill
+
 ## TOOLS TO USE
 
 1. **find_symbol**: Locate the symbol definition

package/dist/skills/type-analysis.js

@@ -12,6 +12,17 @@ export const typeAnalysisSkill = defineSkill({
     description: 'Analyze type hierarchies, interfaces, and their implementations',
     prompt: `You are in TYPE ANALYSIS mode. Analyze type relationships in the codebase.
 
+## When to Use
+- Understanding interface implementations in the codebase
+- Exploring class inheritance hierarchies
+- Finding all concrete implementations of an abstract class
+- Checking which classes implement a specific interface
+
+## When NOT to Use
+- Planning to refactor a type → use refactor-impact skill first
+- Need general file structure → use code-structure skill
+- Looking for a specific symbol definition → use find_symbol directly
+
 ## TOOLS TO USE
 
 1. **get_type_hierarchy**: Analyze inheritance relationships

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/agents-coding-ts",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "TypeScript/JavaScript analysis tools for AI agents - AST-based code analysis, complexity metrics, and type hierarchy",
   "type": "module",
   "main": "dist/index.js",
@@ -65,14 +65,14 @@
     "node": ">=18.0.0"
   },
   "peerDependencies": {
-    "@compilr-dev/agents": "^0.3.0"
+    "@compilr-dev/agents": "^0.3.1"
   },
   "dependencies": {
     "typescript": "^5.3.0"
   },
   "devDependencies": {
     "@anthropic-ai/sdk": "^0.30.1",
-    "@compilr-dev/agents": "^0.3.0",
+    "@compilr-dev/agents": "^0.3.1",
     "@eslint/js": "^9.39.1",
     "@types/node": "^24.10.1",
     "@vitest/coverage-v8": "^3.2.4",