Claude Code RiskExec Setup

A Node.js CLI tool for setting up Claude Code configurations and providing real-time analytics with comprehensive monitoring capabilities.

What This Skill Does

This skill helps you set up and manage Claude Code configurations while providing a powerful analytics dashboard for monitoring active sessions, conversation states, performance metrics, and system health in real-time.

Key Features

Instructions

Initial Setup

1. **Clone and install the repository:**

```bash

git clone <repository-url>

cd claude-code-riskexec

npm install

```

2. **Verify Node.js version (14.0.0+):**

```bash

node --version

```

3. **Run initial tests to verify installation:**

```bash

npm test

```

Starting the Analytics Dashboard

1. **Start the analytics server:**

```bash

npm run analytics:start

```

2. **Open your browser to http://localhost:3333**

3. **Monitor real-time metrics:**

- Active Claude Code conversations

- Conversation states ("Claude working...", "User typing...", "Awaiting input...")

- System performance and memory usage

- Export data as CSV/JSON

Running the CLI Tool

```bash

npm start

```

Development Workflow

1. **For code changes:**

```bash

# Run tests in watch mode

npm run test:watch

# Check syntax

node --check src/analytics.js

```

2. **Before committing:**

```bash

# Run full test suite

npm test

# Run analytics tests

npm run analytics:test

# Check for vulnerabilities

npm audit

```

3. **Component management:**

- Access 600+ specialized agents (frontend-developer, security-auditor, data-scientist)

- Use 200+ slash commands (/setup-ci-cd-pipeline, /generate-tests, /optimize-bundle)

- Integrate MCPs for databases, development tools, and browser automation

- Configure hooks for git operations, notifications, and performance monitoring

BMAD Workflow (Spec Kit)

Use the gated feature development workflow:

```bash

Create functional specification

/specify <feature-name>

Generate technical plan

/plan <feature-name>

Break down into tasks

/tasks <feature-name>

Execute implementation

/implement <feature-name>

```

Specifications are stored in `specs/<feature>/` with constitution rules enforced.

Testing

```bash

Run all tests

npm test

Run specific test suites

npm run test:unit

npm run test:integration

npm run test:e2e

npm run test:analytics

Generate coverage report

npm run test:coverage

```

Project Structure

```

src/

├── index.js # CLI entry point

├── analytics.js # Analytics dashboard server

├── analytics/ # Modular analytics components

│ ├── core/ # StateCalculator, ProcessDetector, ConversationAnalyzer

│ ├── data/ # DataCache

│ ├── notifications/ # WebSocketServer, NotificationManager

│ └── utils/ # PerformanceMonitor

├── analytics-web/ # Frontend components

└── templates/ # Configuration templates

specs/

├── constitution.md # Quality rules and review checklist

└── <feature>/ # Feature specs, plans, and tasks

```

Technology Stack

Important Notes

Security Guidelines

Examples

**Start analytics and monitor a session:**

```bash

npm run analytics:start

Open http://localhost:3333

Start Claude Code in another terminal

Watch real-time state changes in dashboard

```

**Run comprehensive tests:**

```bash

npm run test:all

npm run test:coverage

```

**Set up a new feature with BMAD:**

```bash

/specify user-authentication

/plan user-authentication

/tasks user-authentication

/implement user-authentication

```