@claude-flow/cli 3.42.3 → 3.42.5

package/node_modules/@claude-flow/codex/.agents/skills/performance-analysis/SKILL.md

@@ -1,32 +1,32 @@
----
-name: performance-analysis
-description: >
-  Performance profiling, benchmarking, and optimization.
-  Use when: slow operations, regressions, memory pressure, release validation.
-  Skip when: early prototyping, documentation, configuration-only changes.
----
-
-# Performance Analysis Skill
-
-## Purpose
-Measure before optimizing and preserve reproducible benchmark evidence.
-
-## Commands
-
-### Run Benchmark Suite
-
-```bash
-npx @claude-flow/cli performance benchmark --suite all
-```
-
-### Profile Code
-
-```bash
-npx @claude-flow/cli performance profile --target ./src
-```
-
-## Best Practices
-1. Capture a baseline before changing code
-2. Use identical inputs and environments
-3. Report variance, not only the fastest result
-4. Re-run correctness tests after optimization
+---
+name: performance-analysis
+description: >
+  Performance profiling, benchmarking, and optimization.
+  Use when: slow operations, regressions, memory pressure, release validation.
+  Skip when: early prototyping, documentation, configuration-only changes.
+---
+
+# Performance Analysis Skill
+
+## Purpose
+Measure before optimizing and preserve reproducible benchmark evidence.
+
+## Commands
+
+### Run Benchmark Suite
+
+```bash
+npx @claude-flow/cli performance benchmark --suite all
+```
+
+### Profile Code
+
+```bash
+npx @claude-flow/cli performance profile --target ./src
+```
+
+## Best Practices
+1. Capture a baseline before changing code
+2. Use identical inputs and environments
+3. Report variance, not only the fastest result
+4. Re-run correctness tests after optimization

package/node_modules/@claude-flow/codex/.agents/skills/security-audit/SKILL.md

@@ -1,46 +1,46 @@
----
-name: security-audit
-description: >
-  Security scanning and vulnerability detection.
-  Use when: authentication, authorization, payment processing, user data.
-  Skip when: read-only operations, internal tooling.
----
-
-# Security Audit Skill
-
-## Purpose
-Security scanning and vulnerability detection.
-
-## When to Trigger
-- authentication
-- authorization
-- payment processing
-- user data
-
-## When to Skip
-- read-only operations
-- internal tooling
-
-## Commands
-
-### Full Security Scan
-Run comprehensive security analysis
-
-```bash
-npx @claude-flow/cli security scan --depth full
-```
-
-### Input Validation Check
-Check for input validation issues
-
-```bash
-npx @claude-flow/cli security scan --check input-validation
-```
-
-
-
-## Best Practices
-1. Check memory for existing patterns before starting
-2. Use hierarchical topology for coordination
-3. Store successful patterns after completion
-4. Document any new learnings
+---
+name: security-audit
+description: >
+  Security scanning and vulnerability detection.
+  Use when: authentication, authorization, payment processing, user data.
+  Skip when: read-only operations, internal tooling.
+---
+
+# Security Audit Skill
+
+## Purpose
+Security scanning and vulnerability detection.
+
+## When to Trigger
+- authentication
+- authorization
+- payment processing
+- user data
+
+## When to Skip
+- read-only operations
+- internal tooling
+
+## Commands
+
+### Full Security Scan
+Run comprehensive security analysis
+
+```bash
+npx @claude-flow/cli security scan --depth full
+```
+
+### Input Validation Check
+Check for input validation issues
+
+```bash
+npx @claude-flow/cli security scan --check input-validation
+```
+
+
+
+## Best Practices
+1. Check memory for existing patterns before starting
+2. Use hierarchical topology for coordination
+3. Store successful patterns after completion
+4. Document any new learnings

package/node_modules/@claude-flow/codex/.agents/skills/sparc-methodology/SKILL.md

@@ -1,46 +1,46 @@
----
-name: sparc-methodology
-description: >
-  SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).
-  Use when: new features, complex implementations, architectural changes.
-  Skip when: simple fixes, documentation, configuration.
----
-
-# Sparc Methodology Skill
-
-## Purpose
-SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).
-
-## When to Trigger
-- new features
-- complex implementations
-- architectural changes
-
-## When to Skip
-- simple fixes
-- documentation
-- configuration
-
-## Commands
-
-### Specification Phase
-Define requirements and acceptance criteria
-
-```bash
-npx @claude-flow/cli hooks route --task "specification: [requirements]"
-```
-
-### Architecture Phase
-Design system structure
-
-```bash
-npx @claude-flow/cli hooks route --task "architecture: [design]"
-```
-
-
-
-## Best Practices
-1. Check memory for existing patterns before starting
-2. Use hierarchical topology for coordination
-3. Store successful patterns after completion
-4. Document any new learnings
+---
+name: sparc-methodology
+description: >
+  SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).
+  Use when: new features, complex implementations, architectural changes.
+  Skip when: simple fixes, documentation, configuration.
+---
+
+# Sparc Methodology Skill
+
+## Purpose
+SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).
+
+## When to Trigger
+- new features
+- complex implementations
+- architectural changes
+
+## When to Skip
+- simple fixes
+- documentation
+- configuration
+
+## Commands
+
+### Specification Phase
+Define requirements and acceptance criteria
+
+```bash
+npx @claude-flow/cli hooks route --task "specification: [requirements]"
+```
+
+### Architecture Phase
+Design system structure
+
+```bash
+npx @claude-flow/cli hooks route --task "architecture: [design]"
+```
+
+
+
+## Best Practices
+1. Check memory for existing patterns before starting
+2. Use hierarchical topology for coordination
+3. Store successful patterns after completion
+4. Document any new learnings

package/node_modules/@claude-flow/codex/.agents/skills/swarm-orchestration/SKILL.md

@@ -1,53 +1,53 @@
----
-name: swarm-orchestration
-description: >
-  Multi-agent swarm coordination for complex tasks.
-  Use when: 3+ files need changes, new features, refactoring.
-  Skip when: single file edits, simple fixes, documentation.
----
-
-# Swarm Orchestration Skill
-
-## Purpose
-Multi-agent swarm coordination for complex tasks.
-
-## When to Trigger
-- 3+ files need changes
-- new features
-- refactoring
-
-## When to Skip
-- single file edits
-- simple fixes
-- documentation
-
-## Commands
-
-### Initialize Swarm
-Start a new swarm with hierarchical topology
-
-```bash
-npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8
-```
-
-### Route Task
-Route a task to the appropriate agents
-
-```bash
-npx @claude-flow/cli hooks route --task "[task description]"
-```
-
-### Monitor Status
-Check the current swarm status
-
-```bash
-npx @claude-flow/cli swarm status
-```
-
-
-
-## Best Practices
-1. Check memory for existing patterns before starting
-2. Use hierarchical topology for coordination
-3. Store successful patterns after completion
-4. Document any new learnings
+---
+name: swarm-orchestration
+description: >
+  Multi-agent swarm coordination for complex tasks.
+  Use when: 3+ files need changes, new features, refactoring.
+  Skip when: single file edits, simple fixes, documentation.
+---
+
+# Swarm Orchestration Skill
+
+## Purpose
+Multi-agent swarm coordination for complex tasks.
+
+## When to Trigger
+- 3+ files need changes
+- new features
+- refactoring
+
+## When to Skip
+- single file edits
+- simple fixes
+- documentation
+
+## Commands
+
+### Initialize Swarm
+Start a new swarm with hierarchical topology
+
+```bash
+npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8
+```
+
+### Route Task
+Route a task to the appropriate agents
+
+```bash
+npx @claude-flow/cli hooks route --task "[task description]"
+```
+
+### Monitor Status
+Check the current swarm status
+
+```bash
+npx @claude-flow/cli swarm status
+```
+
+
+
+## Best Practices
+1. Check memory for existing patterns before starting
+2. Use hierarchical topology for coordination
+3. Store successful patterns after completion
+4. Document any new learnings