@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/cc-audit/steps/step-01-scan.md

@@ -1,142 +1,142 @@
----
-name: step-01-scan
-description: Scan all Claude Code components in target directories
-next_step: steps/step-02-analyze.md
----
-
-# Step 1: Scan Components
-
-## MANDATORY EXECUTION RULES:
-- Scan ALL component types (skills, agents, hooks, settings)
-- Record metadata for each component found
-- Do NOT validate yet - just inventory
-
-## YOUR TASK:
-Discover and inventory all Claude Code components in the resolved scan paths.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Scan Skills
-
-For each path in {scan_paths}:
-
-```
-Search for skills:
-  Glob: "{path}/skills/*/SKILL.md"
-
-For each SKILL.md found:
-  Read the file
-  Extract frontmatter fields:
-    - name
-    - description
-    - disable-model-invocation
-    - user-invocable
-    - allowed-tools
-    - model
-    - context
-    - agent
-    - argument-hint
-    - hooks
-
-  Check for supporting directories:
-    Glob: "{skill_dir}/steps/step-*.md" → step_count
-    Glob: "{skill_dir}/templates/*" → template_count
-    Glob: "{skill_dir}/references/*" → reference_count
-    Glob: "{skill_dir}/scripts/*" → script_count
-    Glob: "{skill_dir}/examples/*" → example_count
-
-  Record in {skills_found}:
-    {name, path, frontmatter, step_count, template_count, reference_count, script_count, example_count, line_count}
-```
-
-### 2. Scan Agents
-
-```
-Search for agents:
-  Glob: "{path}/agents/*.md"
-  Glob: "{path}/agents/**/*.md"
-
-For each agent .md found:
-  Read the file
-  Extract frontmatter fields:
-    - name
-    - description
-    - color
-    - model
-    - tools
-    - disallowedTools
-    - permissionMode
-    - skills
-    - hooks
-
-  Record in {agents_found}:
-    {name, path, frontmatter, line_count, category}
-
-  category = parent directory name if nested (e.g., "efcore", "gitflow"), else "root"
-```
-
-### 3. Scan Hooks
-
-```
-Search for hook configurations:
-  Read: "{path}/hooks/hooks.json" (if exists)
-  Read: "{path}/settings.json" → extract "hooks" section
-  Read: "{path}/settings.local.json" → extract "hooks" section (if exists)
-
-For each hook configuration found:
-  Extract events (PreToolUse, PostToolUse, Stop, etc.)
-  For each event:
-    Extract matchers and hook handlers
-    Record type (command, prompt, agent)
-    Record referenced scripts/files
-
-  Record in {hooks_found}:
-    {source_file, event, matcher, type, command_or_prompt, timeout}
-```
-
-### 4. Scan Settings
-
-```
-Read settings files:
-  "{path}/settings.json"
-  "{path}/settings.local.json"
-
-Extract:
-  - permissions (allow, deny, ask rules)
-  - MCP server config
-  - plugin config
-  - environment variables
-  - model settings
-```
-
-### 5. Display Inventory Summary
-
-```
-Component Inventory:
-
-| Type | Count | Scope |
-|------|-------|-------|
-| Skills | {skills_found.length} | {scope} |
-| Agents | {agents_found.length} | {scope} |
-| Hooks | {hooks_found.length} | {scope} |
-| Settings files | N | {scope} |
-
-Skills: {list names}
-Agents: {list names}
-Hooks: {list events}
-
-→ Analyzing components...
-```
-
----
-
-## SUCCESS METRICS:
-- All component types scanned
-- Metadata extracted for each component
-- Counts displayed in summary table
-- No components missed
-
-## NEXT STEP:
-After showing inventory summary, proceed directly to `./step-02-analyze.md`
+---
+name: step-01-scan
+description: Scan all Claude Code components in target directories
+next_step: steps/step-02-analyze.md
+---
+
+# Step 1: Scan Components
+
+## MANDATORY EXECUTION RULES:
+- Scan ALL component types (skills, agents, hooks, settings)
+- Record metadata for each component found
+- Do NOT validate yet - just inventory
+
+## YOUR TASK:
+Discover and inventory all Claude Code components in the resolved scan paths.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Scan Skills
+
+For each path in {scan_paths}:
+
+```
+Search for skills:
+  Glob: "{path}/skills/*/SKILL.md"
+
+For each SKILL.md found:
+  Read the file
+  Extract frontmatter fields:
+    - name
+    - description
+    - disable-model-invocation
+    - user-invocable
+    - allowed-tools
+    - model
+    - context
+    - agent
+    - argument-hint
+    - hooks
+
+  Check for supporting directories:
+    Glob: "{skill_dir}/steps/step-*.md" → step_count
+    Glob: "{skill_dir}/templates/*" → template_count
+    Glob: "{skill_dir}/references/*" → reference_count
+    Glob: "{skill_dir}/scripts/*" → script_count
+    Glob: "{skill_dir}/examples/*" → example_count
+
+  Record in {skills_found}:
+    {name, path, frontmatter, step_count, template_count, reference_count, script_count, example_count, line_count}
+```
+
+### 2. Scan Agents
+
+```
+Search for agents:
+  Glob: "{path}/agents/*.md"
+  Glob: "{path}/agents/**/*.md"
+
+For each agent .md found:
+  Read the file
+  Extract frontmatter fields:
+    - name
+    - description
+    - color
+    - model
+    - tools
+    - disallowedTools
+    - permissionMode
+    - skills
+    - hooks
+
+  Record in {agents_found}:
+    {name, path, frontmatter, line_count, category}
+
+  category = parent directory name if nested (e.g., "efcore", "gitflow"), else "root"
+```
+
+### 3. Scan Hooks
+
+```
+Search for hook configurations:
+  Read: "{path}/hooks/hooks.json" (if exists)
+  Read: "{path}/settings.json" → extract "hooks" section
+  Read: "{path}/settings.local.json" → extract "hooks" section (if exists)
+
+For each hook configuration found:
+  Extract events (PreToolUse, PostToolUse, Stop, etc.)
+  For each event:
+    Extract matchers and hook handlers
+    Record type (command, prompt, agent)
+    Record referenced scripts/files
+
+  Record in {hooks_found}:
+    {source_file, event, matcher, type, command_or_prompt, timeout}
+```
+
+### 4. Scan Settings
+
+```
+Read settings files:
+  "{path}/settings.json"
+  "{path}/settings.local.json"
+
+Extract:
+  - permissions (allow, deny, ask rules)
+  - MCP server config
+  - plugin config
+  - environment variables
+  - model settings
+```
+
+### 5. Display Inventory Summary
+
+```
+Component Inventory:
+
+| Type | Count | Scope |
+|------|-------|-------|
+| Skills | {skills_found.length} | {scope} |
+| Agents | {agents_found.length} | {scope} |
+| Hooks | {hooks_found.length} | {scope} |
+| Settings files | N | {scope} |
+
+Skills: {list names}
+Agents: {list names}
+Hooks: {list events}
+
+→ Analyzing components...
+```
+
+---
+
+## SUCCESS METRICS:
+- All component types scanned
+- Metadata extracted for each component
+- Counts displayed in summary table
+- No components missed
+
+## NEXT STEP:
+After showing inventory summary, proceed directly to `./step-02-analyze.md`

package/templates/skills/cc-audit/steps/step-02-analyze.md

@@ -1,158 +1,158 @@
----
-name: step-02-analyze
-description: Validate component structure, frontmatter, and cross-references
-next_step: steps/step-03-report.md
----
-
-# Step 2: Analyze Components
-
-## MANDATORY EXECUTION RULES:
-- Validate EVERY component found in Step 1
-- Load reference checklists from `references/` directory
-- Record all issues with severity (ERROR, WARN, INFO)
-- Check cross-references between component types
-
-## YOUR TASK:
-Validate each component against official Claude Code conventions and check cross-references.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Load Checklists
-
-```
-Read reference checklists:
-  Read: "references/skill-checklist.md"
-  Read: "references/agent-checklist.md"
-  Read: "references/hook-checklist.md"
-```
-
-### 2. Validate Skills
-
-For each skill in {skills_found}, check:
-
-**Frontmatter (required):**
-- `name` exists and is lowercase, max 64 chars → ERROR if missing
-- `description` exists and is non-empty → ERROR if missing
-
-**Frontmatter (recommended):**
-- `argument-hint` present if skill accepts arguments → WARN if missing
-- `disable-model-invocation` explicitly set for side-effect skills → WARN
-
-**SKILL.md quality:**
-- Line count < 500 → WARN if exceeded
-- Contains `<objective>` section → WARN if missing
-- Contains `<entry_point>` section (if has steps/) → ERROR if missing
-- Contains `<workflow>` or `<step_files>` section → INFO if missing
-
-**Step files validation (if steps/ exists):**
-- Each step file has frontmatter with `name` and `description` → ERROR if missing
-- Each step file (except last) has `next_step` in frontmatter → ERROR if missing
-- `next_step` paths resolve to existing files → ERROR if broken
-- Steps follow sequential naming (step-00, step-01, ...) → WARN if not
-- Each step has "NEXT STEP" or "SUCCESS METRICS" section → INFO if missing
-
-**File references:**
-- All files referenced in SKILL.md exist → ERROR if missing
-- Templates, references, scripts directories referenced exist → WARN if missing
-
-**Record issues in {issues}:**
-```
-{component_name, component_type: "skill", severity, message, file_path, line_number}
-```
-
-### 3. Validate Agents
-
-For each agent in {agents_found}, check:
-
-**Frontmatter (required):**
-- `name` exists → ERROR if missing
-- `description` exists and is non-empty → ERROR if missing
-
-**Frontmatter (recommended):**
-- `model` is valid (haiku, sonnet, opus, inherit) or absent → ERROR if invalid
-- `tools` references valid tool names → WARN if unrecognized tool
-- `permissionMode` is valid (default, acceptEdits, dontAsk, bypassPermissions, plan) → ERROR if invalid
-- `skills` references existing skill names → WARN if not found
-
-**Content quality:**
-- Has workflow or instructions section → INFO if very short (< 10 lines)
-- System prompt is clear and actionable → INFO
-
-**Record issues in {issues}:**
-```
-{component_name, component_type: "agent", severity, message, file_path}
-```
-
-### 4. Validate Hooks
-
-For each hook in {hooks_found}, check:
-
-**Structure:**
-- Event name is valid (SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure, Notification, SubagentStart, SubagentStop, Stop, PreCompact, SessionEnd) → ERROR if invalid
-- Hook type is valid (command, prompt, agent) → ERROR if invalid
-
-**Command hooks:**
-- Referenced script/command exists → ERROR if missing
-- Script is executable (on Unix) → WARN if not
-
-**Prompt hooks:**
-- `prompt` field is non-empty → ERROR if missing
-- `model` is valid if specified → WARN if invalid
-
-**Matcher patterns:**
-- Regex is valid → ERROR if invalid syntax
-- Pattern matches at least one known tool/event → INFO if no match
-
-### 5. Validate Cross-References
-
-```
-Check skills → agents:
-  For skills with `context: fork` and `agent: {name}`:
-    Verify agent exists in {agents_found} or is built-in (Explore, Plan, general-purpose, Bash)
-    → WARN if agent not found
-
-Check agents → skills:
-  For agents with `skills: [...]`:
-    Verify each skill exists in {skills_found}
-    → WARN if skill not found
-
-Check hooks → scripts:
-  For command hooks:
-    Verify referenced script exists on filesystem
-    → ERROR if missing
-
-Check settings → permissions:
-  For permission rules referencing tools:
-    Verify tool names are valid
-    → WARN if unrecognized
-```
-
-### 6. Display Analysis Summary
-
-```
-Analysis Complete:
-
-| Severity | Count |
-|----------|-------|
-| ERROR | {count} |
-| WARN | {count} |
-| INFO | {count} |
-
-Top issues:
-{list top 5 most critical issues}
-
-→ Generating report...
-```
-
----
-
-## SUCCESS METRICS:
-- All components validated against checklists
-- Cross-references checked
-- All issues recorded with severity
-- Summary counts displayed
-
-## NEXT STEP:
-After showing analysis summary, proceed directly to `./step-03-report.md`
+---
+name: step-02-analyze
+description: Validate component structure, frontmatter, and cross-references
+next_step: steps/step-03-report.md
+---
+
+# Step 2: Analyze Components
+
+## MANDATORY EXECUTION RULES:
+- Validate EVERY component found in Step 1
+- Load reference checklists from `references/` directory
+- Record all issues with severity (ERROR, WARN, INFO)
+- Check cross-references between component types
+
+## YOUR TASK:
+Validate each component against official Claude Code conventions and check cross-references.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Load Checklists
+
+```
+Read reference checklists:
+  Read: "references/skill-checklist.md"
+  Read: "references/agent-checklist.md"
+  Read: "references/hook-checklist.md"
+```
+
+### 2. Validate Skills
+
+For each skill in {skills_found}, check:
+
+**Frontmatter (required):**
+- `name` exists and is lowercase, max 64 chars → ERROR if missing
+- `description` exists and is non-empty → ERROR if missing
+
+**Frontmatter (recommended):**
+- `argument-hint` present if skill accepts arguments → WARN if missing
+- `disable-model-invocation` explicitly set for side-effect skills → WARN
+
+**SKILL.md quality:**
+- Line count < 500 → WARN if exceeded
+- Contains `<objective>` section → WARN if missing
+- Contains `<entry_point>` section (if has steps/) → ERROR if missing
+- Contains `<workflow>` or `<step_files>` section → INFO if missing
+
+**Step files validation (if steps/ exists):**
+- Each step file has frontmatter with `name` and `description` → ERROR if missing
+- Each step file (except last) has `next_step` in frontmatter → ERROR if missing
+- `next_step` paths resolve to existing files → ERROR if broken
+- Steps follow sequential naming (step-00, step-01, ...) → WARN if not
+- Each step has "NEXT STEP" or "SUCCESS METRICS" section → INFO if missing
+
+**File references:**
+- All files referenced in SKILL.md exist → ERROR if missing
+- Templates, references, scripts directories referenced exist → WARN if missing
+
+**Record issues in {issues}:**
+```
+{component_name, component_type: "skill", severity, message, file_path, line_number}
+```
+
+### 3. Validate Agents
+
+For each agent in {agents_found}, check:
+
+**Frontmatter (required):**
+- `name` exists → ERROR if missing
+- `description` exists and is non-empty → ERROR if missing
+
+**Frontmatter (recommended):**
+- `model` is valid (haiku, sonnet, opus, inherit) or absent → ERROR if invalid
+- `tools` references valid tool names → WARN if unrecognized tool
+- `permissionMode` is valid (default, acceptEdits, dontAsk, bypassPermissions, plan) → ERROR if invalid
+- `skills` references existing skill names → WARN if not found
+
+**Content quality:**
+- Has workflow or instructions section → INFO if very short (< 10 lines)
+- System prompt is clear and actionable → INFO
+
+**Record issues in {issues}:**
+```
+{component_name, component_type: "agent", severity, message, file_path}
+```
+
+### 4. Validate Hooks
+
+For each hook in {hooks_found}, check:
+
+**Structure:**
+- Event name is valid (SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure, Notification, SubagentStart, SubagentStop, Stop, PreCompact, SessionEnd) → ERROR if invalid
+- Hook type is valid (command, prompt, agent) → ERROR if invalid
+
+**Command hooks:**
+- Referenced script/command exists → ERROR if missing
+- Script is executable (on Unix) → WARN if not
+
+**Prompt hooks:**
+- `prompt` field is non-empty → ERROR if missing
+- `model` is valid if specified → WARN if invalid
+
+**Matcher patterns:**
+- Regex is valid → ERROR if invalid syntax
+- Pattern matches at least one known tool/event → INFO if no match
+
+### 5. Validate Cross-References
+
+```
+Check skills → agents:
+  For skills with `context: fork` and `agent: {name}`:
+    Verify agent exists in {agents_found} or is built-in (Explore, Plan, general-purpose, Bash)
+    → WARN if agent not found
+
+Check agents → skills:
+  For agents with `skills: [...]`:
+    Verify each skill exists in {skills_found}
+    → WARN if skill not found
+
+Check hooks → scripts:
+  For command hooks:
+    Verify referenced script exists on filesystem
+    → ERROR if missing
+
+Check settings → permissions:
+  For permission rules referencing tools:
+    Verify tool names are valid
+    → WARN if unrecognized
+```
+
+### 6. Display Analysis Summary
+
+```
+Analysis Complete:
+
+| Severity | Count |
+|----------|-------|
+| ERROR | {count} |
+| WARN | {count} |
+| INFO | {count} |
+
+Top issues:
+{list top 5 most critical issues}
+
+→ Generating report...
+```
+
+---
+
+## SUCCESS METRICS:
+- All components validated against checklists
+- Cross-references checked
+- All issues recorded with severity
+- Summary counts displayed
+
+## NEXT STEP:
+After showing analysis summary, proceed directly to `./step-03-report.md`