@atlashub/smartstack-cli 3.39.0 → 3.40.0

package/templates/skills/cc-audit/references/hook-checklist.md

@@ -1,110 +1,110 @@
-# Hook Validation Checklist
-
-Based on official Claude Code documentation: https://code.claude.com/docs/en/hooks
-
-## Required
-
-- [ ] Hook configuration is valid JSON
-- [ ] Event name is a valid lifecycle event
-- [ ] At least one hook handler defined per event entry
-
-## Valid Lifecycle Events
-
-| Event | When it fires | Matcher target |
-|-------|---------------|----------------|
-| `SessionStart` | Session begins/resumes | source: startup, resume, clear, compact |
-| `UserPromptSubmit` | Before Claude processes prompt | - |
-| `PreToolUse` | Before tool call | tool name |
-| `PermissionRequest` | Permission dialog appears | tool name |
-| `PostToolUse` | After successful tool call | tool name |
-| `PostToolUseFailure` | After tool failure | tool name |
-| `Notification` | Claude sends notification | type: permission_prompt, idle_prompt |
-| `SubagentStart` | Subagent spawned | agent type name |
-| `SubagentStop` | Subagent finishes | agent type name |
-| `Stop` | Main agent finishes | - |
-| `PreCompact` | Before context compaction | - |
-| `SessionEnd` | Session ends | - |
-
-## Hook Handler Validation
-
-### Command type (`type: "command"`)
-- [ ] `command` field is non-empty
-- [ ] Referenced script/binary exists on filesystem
-- [ ] Script is executable (Unix: chmod +x)
-- [ ] Script handles JSON stdin correctly
-- [ ] Exit codes are meaningful (0=continue, 2=block)
-- [ ] `timeout` set if script might hang (default: varies)
-
-### Prompt type (`type: "prompt"`)
-- [ ] `prompt` field is non-empty and descriptive
-- [ ] `model` is valid if specified (haiku recommended for speed)
-- [ ] `timeout` set appropriately
-
-### Agent type (`type: "agent"`)
-- [ ] Agent configuration is valid
-- [ ] Tools specified for the agent hook
-- [ ] Timeout set to prevent runaway agents
-
-## Matcher Validation
-
-- [ ] Matcher is a valid regex pattern
-- [ ] Matcher is specific enough (avoid `.*` unless intentional)
-- [ ] For tool events: matches known tool names
-- [ ] For SessionStart: matches valid sources
-- [ ] For Notification: matches valid types
-- [ ] For Subagent events: matches valid agent types
-
-## Configuration Locations
-
-| Location | Scope | Priority |
-|----------|-------|----------|
-| `~/.claude/settings.json` | User (all projects) | Low |
-| `.claude/settings.json` | Project (shared) | Medium |
-| `.claude/settings.local.json` | Personal (gitignored) | High |
-| Skill frontmatter `hooks:` | Skill-scoped | Skill only |
-| Agent frontmatter `hooks:` | Agent-scoped | Agent only |
-
-## JSON Input Format (stdin to command hooks)
-
-```json
-{
-  "session_id": "string",
-  "transcript_path": "string",
-  "cwd": "string",
-  "permission_mode": "string",
-  "hook_event_name": "string",
-  "tool_name": "string (for tool events)",
-  "tool_input": { "object (for tool events)" }
-}
-```
-
-## JSON Output Format (stdout from command hooks)
-
-```json
-{
-  "continue": true,
-  "hookSpecificOutput": {
-    "hookEventName": "PreToolUse",
-    "permissionDecision": "allow|deny|block",
-    "permissionDecisionReason": "string"
-  }
-}
-```
-
-## Exit Code Meanings
-
-| Code | Meaning | Behavior |
-|------|---------|----------|
-| 0 | Success | Continue execution |
-| 2 | Blocking error | Prevent action, show error |
-| Other | Non-blocking error | Log warning, continue |
-
-## Best Practices
-
-- [ ] Hooks are fast (< 5 seconds for sync hooks)
-- [ ] Use `async: true` for long-running operations
-- [ ] Use `once: true` for one-time setup hooks
-- [ ] Use `statusMessage` for user visibility
-- [ ] Quote all shell variables in scripts
-- [ ] Use absolute paths or `$CLAUDE_PROJECT_DIR`
-- [ ] Test hooks manually before deploying
+# Hook Validation Checklist
+
+Based on official Claude Code documentation: https://code.claude.com/docs/en/hooks
+
+## Required
+
+- [ ] Hook configuration is valid JSON
+- [ ] Event name is a valid lifecycle event
+- [ ] At least one hook handler defined per event entry
+
+## Valid Lifecycle Events
+
+| Event | When it fires | Matcher target |
+|-------|---------------|----------------|
+| `SessionStart` | Session begins/resumes | source: startup, resume, clear, compact |
+| `UserPromptSubmit` | Before Claude processes prompt | - |
+| `PreToolUse` | Before tool call | tool name |
+| `PermissionRequest` | Permission dialog appears | tool name |
+| `PostToolUse` | After successful tool call | tool name |
+| `PostToolUseFailure` | After tool failure | tool name |
+| `Notification` | Claude sends notification | type: permission_prompt, idle_prompt |
+| `SubagentStart` | Subagent spawned | agent type name |
+| `SubagentStop` | Subagent finishes | agent type name |
+| `Stop` | Main agent finishes | - |
+| `PreCompact` | Before context compaction | - |
+| `SessionEnd` | Session ends | - |
+
+## Hook Handler Validation
+
+### Command type (`type: "command"`)
+- [ ] `command` field is non-empty
+- [ ] Referenced script/binary exists on filesystem
+- [ ] Script is executable (Unix: chmod +x)
+- [ ] Script handles JSON stdin correctly
+- [ ] Exit codes are meaningful (0=continue, 2=block)
+- [ ] `timeout` set if script might hang (default: varies)
+
+### Prompt type (`type: "prompt"`)
+- [ ] `prompt` field is non-empty and descriptive
+- [ ] `model` is valid if specified (haiku recommended for speed)
+- [ ] `timeout` set appropriately
+
+### Agent type (`type: "agent"`)
+- [ ] Agent configuration is valid
+- [ ] Tools specified for the agent hook
+- [ ] Timeout set to prevent runaway agents
+
+## Matcher Validation
+
+- [ ] Matcher is a valid regex pattern
+- [ ] Matcher is specific enough (avoid `.*` unless intentional)
+- [ ] For tool events: matches known tool names
+- [ ] For SessionStart: matches valid sources
+- [ ] For Notification: matches valid types
+- [ ] For Subagent events: matches valid agent types
+
+## Configuration Locations
+
+| Location | Scope | Priority |
+|----------|-------|----------|
+| `~/.claude/settings.json` | User (all projects) | Low |
+| `.claude/settings.json` | Project (shared) | Medium |
+| `.claude/settings.local.json` | Personal (gitignored) | High |
+| Skill frontmatter `hooks:` | Skill-scoped | Skill only |
+| Agent frontmatter `hooks:` | Agent-scoped | Agent only |
+
+## JSON Input Format (stdin to command hooks)
+
+```json
+{
+  "session_id": "string",
+  "transcript_path": "string",
+  "cwd": "string",
+  "permission_mode": "string",
+  "hook_event_name": "string",
+  "tool_name": "string (for tool events)",
+  "tool_input": { "object (for tool events)" }
+}
+```
+
+## JSON Output Format (stdout from command hooks)
+
+```json
+{
+  "continue": true,
+  "hookSpecificOutput": {
+    "hookEventName": "PreToolUse",
+    "permissionDecision": "allow|deny|block",
+    "permissionDecisionReason": "string"
+  }
+}
+```
+
+## Exit Code Meanings
+
+| Code | Meaning | Behavior |
+|------|---------|----------|
+| 0 | Success | Continue execution |
+| 2 | Blocking error | Prevent action, show error |
+| Other | Non-blocking error | Log warning, continue |
+
+## Best Practices
+
+- [ ] Hooks are fast (< 5 seconds for sync hooks)
+- [ ] Use `async: true` for long-running operations
+- [ ] Use `once: true` for one-time setup hooks
+- [ ] Use `statusMessage` for user visibility
+- [ ] Quote all shell variables in scripts
+- [ ] Use absolute paths or `$CLAUDE_PROJECT_DIR`
+- [ ] Test hooks manually before deploying

package/templates/skills/cc-audit/references/skill-checklist.md

@@ -1,70 +1,70 @@
-# Skill Validation Checklist
-
-Based on official Claude Code documentation: https://code.claude.com/docs/en/skills
-
-## Required
-
-- [ ] `SKILL.md` exists in skill directory
-- [ ] Frontmatter contains `name` (lowercase, max 64 chars)
-- [ ] Frontmatter contains `description` (non-empty, describes when to use)
-
-## Recommended
-
-- [ ] `description` uses natural language keywords for auto-detection
-- [ ] `argument-hint` present if skill accepts arguments
-- [ ] `disable-model-invocation: true` set for side-effect operations (deploy, commit, publish)
-- [ ] `user-invocable` explicitly set (true for /commands, false for background knowledge)
-- [ ] `allowed-tools` specified if skill needs tool access without permission prompts
-- [ ] `model` specified if skill needs a specific model (haiku for speed, opus for quality)
-
-## Structure
-
-- [ ] SKILL.md is under 500 lines
-- [ ] Supporting files in appropriate directories:
-  - `templates/` for code templates
-  - `references/` for documentation
-  - `scripts/` for executable scripts
-  - `examples/` for example outputs
-  - `steps/` for progressive step loading
-
-## Progressive Step Loading (if applicable)
-
-- [ ] `<entry_point>` section in SKILL.md points to first step
-- [ ] `<step_files>` section lists all steps with purpose
-- [ ] Each step file has YAML frontmatter with `name` and `description`
-- [ ] Each step (except last) has `next_step` in frontmatter
-- [ ] All `next_step` paths resolve to existing files
-- [ ] Steps follow sequential naming: step-00-*, step-01-*, ...
-- [ ] Each step has sections: YOUR TASK, EXECUTION SEQUENCE, SUCCESS METRICS, NEXT STEP
-- [ ] State variables documented in `<state_variables>` section
-
-## Forked Context (if applicable)
-
-- [ ] `context: fork` set in frontmatter
-- [ ] `agent` field specifies valid agent (Explore, Plan, general-purpose, or custom)
-- [ ] `allowed-tools` lists tools the forked context can use
-- [ ] Custom agent exists if referenced
-
-## Content Quality
-
-- [ ] Has `<objective>` section explaining what the skill does
-- [ ] Has `<quick_start>` with usage examples
-- [ ] Has `<workflow>` describing high-level flow
-- [ ] Has `<execution_rules>` with key constraints
-- [ ] Has `<success_criteria>` defining completion
-- [ ] All file references in content point to existing files
-
-## Frontmatter Fields Reference
-
-| Field | Type | Required | Default | Description |
-|-------|------|----------|---------|-------------|
-| `name` | string | YES | - | Lowercase identifier, max 64 chars |
-| `description` | string | YES | - | When/why Claude should use this skill |
-| `disable-model-invocation` | bool | no | false | true = manual /command only |
-| `user-invocable` | bool | no | true | false = hidden from /menu |
-| `allowed-tools` | string | no | - | CSV of tools without permission prompts |
-| `model` | string | no | inherit | inherit/sonnet/opus/haiku |
-| `context` | string | no | - | "fork" for isolated subagent |
-| `agent` | string | no | - | Subagent type if context: fork |
-| `argument-hint` | string | no | - | Autocomplete hint text |
-| `hooks` | object | no | - | Lifecycle hooks (PreToolUse, etc.) |
+# Skill Validation Checklist
+
+Based on official Claude Code documentation: https://code.claude.com/docs/en/skills
+
+## Required
+
+- [ ] `SKILL.md` exists in skill directory
+- [ ] Frontmatter contains `name` (lowercase, max 64 chars)
+- [ ] Frontmatter contains `description` (non-empty, describes when to use)
+
+## Recommended
+
+- [ ] `description` uses natural language keywords for auto-detection
+- [ ] `argument-hint` present if skill accepts arguments
+- [ ] `disable-model-invocation: true` set for side-effect operations (deploy, commit, publish)
+- [ ] `user-invocable` explicitly set (true for /commands, false for background knowledge)
+- [ ] `allowed-tools` specified if skill needs tool access without permission prompts
+- [ ] `model` specified if skill needs a specific model (haiku for speed, opus for quality)
+
+## Structure
+
+- [ ] SKILL.md is under 500 lines
+- [ ] Supporting files in appropriate directories:
+  - `templates/` for code templates
+  - `references/` for documentation
+  - `scripts/` for executable scripts
+  - `examples/` for example outputs
+  - `steps/` for progressive step loading
+
+## Progressive Step Loading (if applicable)
+
+- [ ] `<entry_point>` section in SKILL.md points to first step
+- [ ] `<step_files>` section lists all steps with purpose
+- [ ] Each step file has YAML frontmatter with `name` and `description`
+- [ ] Each step (except last) has `next_step` in frontmatter
+- [ ] All `next_step` paths resolve to existing files
+- [ ] Steps follow sequential naming: step-00-*, step-01-*, ...
+- [ ] Each step has sections: YOUR TASK, EXECUTION SEQUENCE, SUCCESS METRICS, NEXT STEP
+- [ ] State variables documented in `<state_variables>` section
+
+## Forked Context (if applicable)
+
+- [ ] `context: fork` set in frontmatter
+- [ ] `agent` field specifies valid agent (Explore, Plan, general-purpose, or custom)
+- [ ] `allowed-tools` lists tools the forked context can use
+- [ ] Custom agent exists if referenced
+
+## Content Quality
+
+- [ ] Has `<objective>` section explaining what the skill does
+- [ ] Has `<quick_start>` with usage examples
+- [ ] Has `<workflow>` describing high-level flow
+- [ ] Has `<execution_rules>` with key constraints
+- [ ] Has `<success_criteria>` defining completion
+- [ ] All file references in content point to existing files
+
+## Frontmatter Fields Reference
+
+| Field | Type | Required | Default | Description |
+|-------|------|----------|---------|-------------|
+| `name` | string | YES | - | Lowercase identifier, max 64 chars |
+| `description` | string | YES | - | When/why Claude should use this skill |
+| `disable-model-invocation` | bool | no | false | true = manual /command only |
+| `user-invocable` | bool | no | true | false = hidden from /menu |
+| `allowed-tools` | string | no | - | CSV of tools without permission prompts |
+| `model` | string | no | inherit | inherit/sonnet/opus/haiku |
+| `context` | string | no | - | "fork" for isolated subagent |
+| `agent` | string | no | - | Subagent type if context: fork |
+| `argument-hint` | string | no | - | Autocomplete hint text |
+| `hooks` | object | no | - | Lifecycle hooks (PreToolUse, etc.) |

package/templates/skills/cc-audit/steps/step-00-init.md

@@ -1,98 +1,98 @@
----
-name: step-00-init
-description: Parse scope argument, detect environment, resolve scan paths
-next_step: steps/step-01-scan.md
----
-
-# Step 0: Initialization
-
-## MANDATORY EXECUTION RULES:
-- NEVER skip scope detection
-- ALWAYS resolve actual filesystem paths before proceeding
-- YOU ARE AN INITIALIZER, not a scanner
-
-## YOUR TASK:
-Parse the scope argument, detect the environment, and resolve which directories to scan.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Parse Input
-
-```
-Arguments from $ARGUMENTS:
-  First word → {scope} (default: "project")
-  --fix      → {fix_mode} = true (default: false)
-  --verbose  → {verbose} = true (default: false)
-
-Valid scopes:
-  "project"   → .claude/ in current working directory
-  "global"    → ~/.claude/ (user-level)
-  "templates" → templates/ (SmartStack CLI source only)
-  "all"       → all of the above
-```
-
-### 2. Detect Environment
-
-```
-Use Bash to determine:
-  - Current working directory
-  - Home directory (for global scope)
-  - Is this a SmartStack CLI project? (check for templates/ directory)
-  - Is this a Claude Code project? (check for .claude/ directory)
-```
-
-### 3. Resolve Scan Paths
-
-```
-Based on {scope}:
-
-  "project" →
-    {scan_paths} = ["{cwd}/.claude/"]
-    Verify .claude/ exists, warn if missing
-
-  "global" →
-    {scan_paths} = ["~/.claude/"]
-    Resolve ~ to actual home directory
-
-  "templates" →
-    {scan_paths} = ["{cwd}/templates/"]
-    Only valid in SmartStack CLI project
-
-  "all" →
-    {scan_paths} = combination of applicable paths
-```
-
-### 4. Validate Paths
-
-For each path in {scan_paths}:
-- Use Bash `ls` to verify directory exists
-- If missing: record as warning, skip that path
-- If empty: record as info, skip that path
-
-### 5. Show Summary and Proceed
-
-```
-Audit Configuration:
-
-| Setting | Value |
-|---------|-------|
-| Scope | {scope} |
-| Fix mode | {fix_mode} |
-| Verbose | {verbose} |
-| Paths to scan | {scan_paths} |
-
-→ Scanning components...
-```
-
----
-
-## SUCCESS METRICS:
-- Scope correctly parsed
-- All paths resolved and validated
-- Environment detected (SmartStack CLI vs generic Claude Code project)
-- Summary displayed
-
-## NEXT STEP:
-After showing initialization summary, proceed directly to `./step-01-scan.md`
+---
+name: step-00-init
+description: Parse scope argument, detect environment, resolve scan paths
+next_step: steps/step-01-scan.md
+---
+
+# Step 0: Initialization
+
+## MANDATORY EXECUTION RULES:
+- NEVER skip scope detection
+- ALWAYS resolve actual filesystem paths before proceeding
+- YOU ARE AN INITIALIZER, not a scanner
+
+## YOUR TASK:
+Parse the scope argument, detect the environment, and resolve which directories to scan.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Parse Input
+
+```
+Arguments from $ARGUMENTS:
+  First word → {scope} (default: "project")
+  --fix      → {fix_mode} = true (default: false)
+  --verbose  → {verbose} = true (default: false)
+
+Valid scopes:
+  "project"   → .claude/ in current working directory
+  "global"    → ~/.claude/ (user-level)
+  "templates" → templates/ (SmartStack CLI source only)
+  "all"       → all of the above
+```
+
+### 2. Detect Environment
+
+```
+Use Bash to determine:
+  - Current working directory
+  - Home directory (for global scope)
+  - Is this a SmartStack CLI project? (check for templates/ directory)
+  - Is this a Claude Code project? (check for .claude/ directory)
+```
+
+### 3. Resolve Scan Paths
+
+```
+Based on {scope}:
+
+  "project" →
+    {scan_paths} = ["{cwd}/.claude/"]
+    Verify .claude/ exists, warn if missing
+
+  "global" →
+    {scan_paths} = ["~/.claude/"]
+    Resolve ~ to actual home directory
+
+  "templates" →
+    {scan_paths} = ["{cwd}/templates/"]
+    Only valid in SmartStack CLI project
+
+  "all" →
+    {scan_paths} = combination of applicable paths
+```
+
+### 4. Validate Paths
+
+For each path in {scan_paths}:
+- Use Bash `ls` to verify directory exists
+- If missing: record as warning, skip that path
+- If empty: record as info, skip that path
+
+### 5. Show Summary and Proceed
+
+```
+Audit Configuration:
+
+| Setting | Value |
+|---------|-------|
+| Scope | {scope} |
+| Fix mode | {fix_mode} |
+| Verbose | {verbose} |
+| Paths to scan | {scan_paths} |
+
+→ Scanning components...
+```
+
+---
+
+## SUCCESS METRICS:
+- Scope correctly parsed
+- All paths resolved and validated
+- Environment detected (SmartStack CLI vs generic Claude Code project)
+- Summary displayed
+
+## NEXT STEP:
+After showing initialization summary, proceed directly to `./step-01-scan.md`