Skip to content

fix: correct script path references in skills and agents #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tkavelli wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: correct script path references in skills and agents #138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/agents/agentica-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ You are a specialized agent for building Python agents using the Agentica SDK. Y
Before starting, read the SDK skill for full API reference:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/agentica-sdk/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/agentica-sdk/SKILL.md
```

## Step 2: Understand Your Task
Expand Down
4 changes: 2 additions & 2 deletions .claude/agents/braintrust-analyst.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,15 @@ You are a specialized analysis agent. Your job is to run Braintrust analysis scr
Read the braintrust-analyze skill:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/braintrust-analyze/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/braintrust-analyze/SKILL.md
```

## Step 2: Execute Analysis

Run analysis IMMEDIATELY using Bash tool:

```bash
cd $CLAUDE_PROJECT_DIR && uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
cd $CLAUDE_OPC_DIR && uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
```

Other analyses (run as needed):
Expand Down
2 changes: 1 addition & 1 deletion .claude/agents/debug-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ You are a specialized debugging agent. Your job is to investigate issues, trace
Before starting, read the debug skill for methodology:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/debug/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/debug/SKILL.md
```

Follow the structure and guidelines from that skill.
Expand Down
10 changes: 5 additions & 5 deletions .claude/agents/memory-extractor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ You receive:

```bash
# Use the extraction script with filtering
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
(cd $CLAUDE_OPC_DIR && uv run python scripts/core/extract_thinking_blocks.py \
--jsonl "$JSONL_PATH" \
--filter \
--format json) > /tmp/perception-blocks.json
Expand All @@ -42,7 +42,7 @@ This extracts only thinking blocks containing perception signals (actually, real
### Step 2: Check Stats

```bash
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
(cd $CLAUDE_OPC_DIR && uv run python scripts/core/extract_thinking_blocks.py \
--jsonl "$JSONL_PATH" \
--stats)
```
Expand Down Expand Up @@ -80,7 +80,7 @@ For each extracted perception change, use the mapped type from Step 3:

```bash
# Example for a CORRECTION → ERROR_FIX
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
(cd $CLAUDE_OPC_DIR && uv run python scripts/core/store_learning.py \
--session-id "$SESSION_ID" \
--type "ERROR_FIX" \
--context "what this relates to" \
Expand All @@ -90,7 +90,7 @@ For each extracted perception change, use the mapped type from Step 3:
--json)

# Example for a REALIZATION/INSIGHT → CODEBASE_PATTERN
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
(cd $CLAUDE_OPC_DIR && uv run python scripts/core/store_learning.py \
--session-id "$SESSION_ID" \
--type "CODEBASE_PATTERN" \
--context "what this relates to" \
Expand All @@ -100,7 +100,7 @@ For each extracted perception change, use the mapped type from Step 3:
--json)

# Example for a DEBUGGING_APPROACH → WORKING_SOLUTION
(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
(cd $CLAUDE_OPC_DIR && uv run python scripts/core/store_learning.py \
--session-id "$SESSION_ID" \
--type "WORKING_SOLUTION" \
--context "debugging methodology" \
Expand Down
2 changes: 1 addition & 1 deletion .claude/agents/plan-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ You are a specialized planning agent. Your job is to create detailed implementat
Before creating any plan, read the planning skill for methodology and format:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/create_plan/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/create_plan/SKILL.md
```

Follow the structure and guidelines from that skill.
Expand Down
4 changes: 2 additions & 2 deletions .claude/agents/scribe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,10 @@ Before creating documentation, read the relevant skills:

```bash
# For handoffs
cat $CLAUDE_PROJECT_DIR/.claude/skills/create_handoff/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/create_handoff/SKILL.md

# For ledger updates
cat $CLAUDE_PROJECT_DIR/.claude/skills/continuity_ledger/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/continuity_ledger/SKILL.md
```

Follow the structure and guidelines from those skills.
Expand Down
4 changes: 2 additions & 2 deletions .claude/agents/session-analyst.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,15 +13,15 @@ You analyze Claude Code session data from Braintrust and provide insights.
Read the skill file first:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/braintrust-analyze/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/braintrust-analyze/SKILL.md
```

## Step 2: Run Analysis

Run the appropriate command based on user request:

```bash
cd $CLAUDE_PROJECT_DIR
cd $CLAUDE_OPC_DIR
uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
```

Expand Down
2 changes: 1 addition & 1 deletion .claude/agents/validate-agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ You are a specialized validation agent. Your job is to validate a technical plan
Before validating, read the validation skill for methodology and format:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/validate-agent/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/validate-agent/SKILL.md
```

Follow the structure and guidelines from that skill.
Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/commit/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ You are tasked with creating git commits for the changes made during this sessio
- Show the result with `git log --oneline -n [number]`

5. **Generate reasoning (after each commit):**
- Run: `bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"`
- Run: `bash "$CLAUDE_CC_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"`
- This captures what was tried during development (build failures, fixes)
- The reasoning file helps future sessions understand past decisions
- Stored in `.git/claude/commits/<hash>/reasoning.md`
Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/commit/SKILL.v6.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ eta |-> generate_reasoning(hash, message)
```bash
git add <file1> <file2> ...
git commit -m "message"
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
bash "$CLAUDE_CC_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
git log --oneline -n N
```

Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/describe_pr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ You are tasked with generating a comprehensive pull request description followin

4b. **Gather reasoning history (if available):**
- Check if reasoning files exist: `ls .git/claude/commits/*/reasoning.md 2>/dev/null`
- If they exist, aggregate them: `bash "$CLAUDE_PROJECT_DIR/.claude/scripts/aggregate-reasoning.sh" main`
- If they exist, aggregate them: `bash "$CLAUDE_CC_DIR/.claude/scripts/aggregate-reasoning.sh" main`
- This shows what approaches were tried before the final solution
- Save the output for inclusion in the PR description

Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/git-commits/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ When you see these in user prompts, use the commit skill:

The skill will prompt you to run:
```bash
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
bash "$CLAUDE_CC_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
```

Then push if requested:
Expand Down
16 changes: 8 additions & 8 deletions .claude/skills/math-unified/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ For formal proofs, use `/prove` instead.

### SymPy (Symbolic Math)
```bash
uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/sympy_compute.py" <command> <args>
uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/sympy_compute.py" <command> <args>
```

| Command | Description | Example |
Expand Down Expand Up @@ -83,7 +83,7 @@ uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/sympy_compute.py" <co

### Z3 (Constraint Solving)
```bash
uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/z3_solve.py" <command> <args>
uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/z3_solve.py" <command> <args>
```

| Command | Use Case |
Expand All @@ -96,7 +96,7 @@ uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/z3_solve.py" <command

### Pint (Units)
```bash
uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/pint_compute.py" convert <value> <from_unit> <to_unit>
uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/pint_compute.py" convert <value> <from_unit> <to_unit>
```

Example: `convert 5 miles kilometers`
Expand All @@ -105,7 +105,7 @@ Example: `convert 5 miles kilometers`

### Math Router (Auto-Route)
```bash
uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/math_router.py" route "<natural language request>"
uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/math_router.py" route "<natural language request>"
```

Returns the exact command to run. Use when unsure which script.
Expand Down Expand Up @@ -154,28 +154,28 @@ I decide based on your request:
### Solve Equation
```
User: Solve x² - 5x + 6 = 0
Claude: uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/sympy_compute.py" solve "x**2 - 5*x + 6" --var x
Claude: uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/sympy_compute.py" solve "x**2 - 5*x + 6" --var x
Result: x = 2 or x = 3
```

### Compute Eigenvalues
```
User: Find eigenvalues of [[2, 1], [1, 2]]
Claude: uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/sympy_compute.py" eigenvalues "[[2,1],[1,2]]"
Claude: uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/sympy_compute.py" eigenvalues "[[2,1],[1,2]]"
Result: {1: 1, 3: 1} (eigenvalue 1 with multiplicity 1, eigenvalue 3 with multiplicity 1)
```

### Prove Inequality
```
User: Is x² + y² ≥ 2xy always true?
Claude: uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/z3_solve.py" prove "x**2 + y**2 >= 2*x*y"
Claude: uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/z3_solve.py" prove "x**2 + y**2 >= 2*x*y"
Result: PROVED (equivalent to (x-y)² ≥ 0)
```

### Convert Units
```
User: How many kilometers in 26.2 miles?
Claude: uv run python "$CLAUDE_PROJECT_DIR/.claude/scripts/cc_math/pint_compute.py" convert 26.2 miles kilometers
Claude: uv run python "$CLAUDE_OPC_DIR/scripts/cc_math/pint_compute.py" convert 26.2 miles kilometers
Result: 42.16 km
```

Expand Down
4 changes: 2 additions & 2 deletions .claude/skills/recall-reasoning/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ This searches handoffs with post-mortems (what worked, what failed, key decision
### Secondary: Reasoning Files (build attempts)

```bash
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/search-reasoning.sh" "<query>"
bash "$CLAUDE_CC_DIR/.claude/scripts/search-reasoning.sh" "<query>"
```

This searches `.git/claude/commits/*/reasoning.md` for build failures and fixes.
Expand All @@ -50,7 +50,7 @@ uv run python scripts/core/artifact_query.py "implement agent" --outcome SUCCEED
uv run python scripts/core/artifact_query.py "hook implementation" --outcome FAILED

# Search build/test reasoning
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/search-reasoning.sh" "TypeError"
bash "$CLAUDE_CC_DIR/.claude/scripts/search-reasoning.sh" "TypeError"
```

## What Gets Searched
Expand Down
16 changes: 8 additions & 8 deletions .claude/skills/skill-developer/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,14 +56,14 @@ To create a new MCP chain script and wrap it as a skill:
Copy the multi-tool-pipeline template:

```bash
cp $CLAUDE_PROJECT_DIR/scripts/multi_tool_pipeline.py $CLAUDE_PROJECT_DIR/scripts/my_pipeline.py
cp $CLAUDE_OPC_DIR/scripts/multi_tool_pipeline.py $CLAUDE_OPC_DIR/scripts/my_pipeline.py
```

Reference the template pattern:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/multi-tool-pipeline/SKILL.md
cat $CLAUDE_PROJECT_DIR/scripts/multi_tool_pipeline.py
cat $CLAUDE_CC_DIR/.claude/skills/multi-tool-pipeline/SKILL.md
cat $CLAUDE_OPC_DIR/scripts/multi_tool_pipeline.py
```
Comment on lines +59 to 67
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find template files that the review comment references

# Check for multi_tool_pipeline.py in any scripts directory
fd --type f 'multi_tool_pipeline.py'

# Check for multi-tool-pipeline SKILL.md
fd --type f --path '*multi-tool-pipeline*' 'SKILL.md'

# List structure around scripts directories
fd --type d 'scripts' | head -20

Repository: parcadei/Continuous-Claude-v3

Length of output: 371

🏁 Script executed:

#!/bin/bash
# Read the actual SKILL.md file to verify the changes mentioned in the review
cat -n .claude/skills/skill-developer/SKILL.md | sed -n '55,70p'
cat -n .claude/skills/skill-developer/SKILL.md | sed -n '80,90p'
cat -n .claude/skills/skill-developer/SKILL.md | sed -n '140,165p'

Repository: parcadei/Continuous-Claude-v3

Length of output: 1559

🏁 Script executed:

#!/bin/bash
# Check if CLAUDE_CC_DIR and CLAUDE_OPC_DIR are defined/exported
fd --type f 'wizard' | head -10
fd --type f -e 'sh' -e 'bash' | xargs grep -l 'CLAUDE_CC_DIR\|CLAUDE_OPC_DIR' 2>/dev/null | head -10

Repository: parcadei/Continuous-Claude-v3

Length of output: 100

🏁 Script executed:

#!/bin/bash
# Check for all referenced template files

# Check for multi-tool-pipeline skill documentation
fd 'multi-tool-pipeline' --type d

# Check for rules files
fd 'skill-development.md' --type f
fd 'mcp-scripts.md' --type f

# Check for example skills
fd 'SKILL.md' --type f | grep -E '(multi-tool-pipeline|commit|firecrawl-scrape)'

Repository: parcadei/Continuous-Claude-v3

Length of output: 55

🏁 Script executed:

#!/bin/bash
# Check if CLAUDE_CC_DIR and CLAUDE_OPC_DIR are defined in wizard.py
cat -n opc/scripts/setup/wizard.py | grep -E 'CLAUDE_CC_DIR|CLAUDE_OPC_DIR' | head -20

Repository: parcadei/Continuous-Claude-v3

Length of output: 1059

🏁 Script executed:

#!/bin/bash
# Verify the file structure exists
ls -la .claude/skills/ 2>/dev/null | head -20
ls -la .claude/rules/ 2>/dev/null | head -20

Repository: parcadei/Continuous-Claude-v3

Length of output: 2337

🏁 Script executed:

#!/bin/bash
# More specific check for multi-tool-pipeline
find .claude/skills -type d -name "*multi*" 2>/dev/null

# Check all SKILL.md files to see what exists
fd 'SKILL.md' --type f

Repository: parcadei/Continuous-Claude-v3

Length of output: 55

🏁 Script executed:

#!/bin/bash
# Check what's actually in .claude/rules
cat -n .claude/rules/*.md | head -30

Repository: parcadei/Continuous-Claude-v3

Length of output: 1214

Multiple referenced files do not exist; instructions are broken.

The path updates use correct environment variables (confirmed: CLAUDE_CC_DIR and CLAUDE_OPC_DIR are defined in wizard.py), but the referenced files are missing:

  • Line 65: $CLAUDE_CC_DIR/.claude/skills/multi-tool-pipeline/SKILL.md — directory does not exist
  • Line 143: $CLAUDE_CC_DIR/.claude/rules/skill-development.md — file does not exist (actual rules are: agent-memory-recall.md, agent-model-selection.md, claim-verification.md, etc.)
  • Line 144: $CLAUDE_CC_DIR/.claude/rules/mcp-scripts.md — file does not exist
  • Lines 161-162: Example skills commit/SKILL.md and firecrawl-scrape/SKILL.md — neither directory exists

Additionally, line 85 has a duplicate heading: "### Step 2" should be "### Step 3".

Users following these instructions will encounter file-not-found errors. Either create the missing template/example files or correct the references.

🤖 Prompt for AI Agents 
In @.claude/skills/skill-developer/SKILL.md around lines 59 - 67, Update
.claude/skills/skill-developer/SKILL.md so referenced template/example files and
headings are correct: replace or remove references to nonexistent paths
($CLAUDE_CC_DIR/.claude/skills/multi-tool-pipeline/SKILL.md,
$CLAUDE_CC_DIR/.claude/rules/skill-development.md,
$CLAUDE_CC_DIR/.claude/rules/mcp-scripts.md, commit/SKILL.md,
firecrawl-scrape/SKILL.md) and point them to existing files (or add the missing
template files), and fix the duplicate section heading "### Step 2" at line ~85
to "### Step 3"; verify wizard.py environment vars are still used but do not
rely on nonexistent files so users won't hit file-not-found errors.


### Step 2: Customize the Script
Expand Down Expand Up @@ -140,8 +140,8 @@ Add to `.claude/skills/skill-rules.json`:
For full details, read:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/rules/skill-development.md
cat $CLAUDE_PROJECT_DIR/.claude/rules/mcp-scripts.md
cat $CLAUDE_CC_DIR/.claude/rules/skill-development.md
cat $CLAUDE_CC_DIR/.claude/rules/mcp-scripts.md
Comment on lines +143 to +144
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify reference documentation files exist

echo "=== Searching for skill-development.md ==="
fd --type f --full-path '.claude/rules/skill-development.md$' 2>&1 || echo "Not found"

echo ""
echo "=== Searching for mcp-scripts.md ==="
fd --type f --full-path '.claude/rules/mcp-scripts.md$' 2>&1 || echo "Not found"

echo ""
echo "=== All files under .claude/rules directory ==="
fd --type f '.claude/rules/' 2>&1 || echo "Directory not found"

Repository: parcadei/Continuous-Claude-v3

Length of output: 584

🏁 Script executed:

#!/bin/bash
# Broader search to understand the structure

echo "=== Checking if .claude/rules directory exists ==="
fd . '.claude/rules/' 2>&1 | head -20

echo ""
echo "=== Finding SKILL.md file ==="
fd --type f 'SKILL.md$' 2>&1

echo ""
echo "=== All files under .claude directory ==="
fd . '.claude/' 2>&1 | head -30

echo ""
echo "=== Searching for skill-development or skill development files ==="
fd --type f -i 'skill.*development' 2>&1

echo ""
echo "=== Searching for mcp-scripts files ==="
fd --type f -i 'mcp.*scripts' 2>&1

Repository: parcadei/Continuous-Claude-v3

Length of output: 1560

🏁 Script executed:

#!/bin/bash
# More comprehensive search for SKILL.md

echo "=== Recursive search for any SKILL.md file ==="
find . -type f -name 'SKILL.md' 2>/dev/null

echo ""
echo "=== Searching in skill-developer directory ==="
fd . 'skill-developer' 2>&1 | head -30

echo ""
echo "=== All markdown files in .claude ==="
find .claude -type f -name '*.md' 2>/dev/null | sort

Repository: parcadei/Continuous-Claude-v3

Length of output: 17131

🏁 Script executed:

#!/bin/bash
# Check the specific lines in skill-developer SKILL.md

echo "=== Lines around 143-144 in ./.claude/skills/skill-developer/SKILL.md ==="
sed -n '140,150p' ./.claude/skills/skill-developer/SKILL.md

echo ""
echo "=== Total line count ==="
wc -l ./.claude/skills/skill-developer/SKILL.md

Repository: parcadei/Continuous-Claude-v3

Length of output: 468

Create missing reference documentation files or update paths to existing documentation.

The referenced files do not exist at the specified paths:

  • .claude/rules/skill-development.md — does not exist
  • .claude/rules/mcp-scripts.md — does not exist

Either create these files in .claude/rules/ or update the paths in lines 143-144 to reference existing documentation.

🤖 Prompt for AI Agents 
In @.claude/skills/skill-developer/SKILL.md around lines 143 - 144, The SKILL.md
references two missing docs (.claude/rules/skill-development.md and
.claude/rules/mcp-scripts.md); either add those markdown files under
.claude/rules/ with the expected content or update the references in SKILL.md
(lines that call `cat $CLAUDE_CC_DIR/.claude/rules/skill-development.md` and
`cat $CLAUDE_CC_DIR/.claude/rules/mcp-scripts.md`) to point to the correct
existing file paths or filenames; ensure the referenced filenames exactly match
the created file names and commit the new files or the updated SKILL.md
references.

```

## Quick Checklist
Expand All @@ -157,7 +157,7 @@ cat $CLAUDE_PROJECT_DIR/.claude/rules/mcp-scripts.md
Look at existing skills for patterns:

```bash
ls $CLAUDE_PROJECT_DIR/.claude/skills/
cat $CLAUDE_PROJECT_DIR/.claude/skills/commit/SKILL.md
cat $CLAUDE_PROJECT_DIR/.claude/skills/firecrawl-scrape/SKILL.md
ls $CLAUDE_CC_DIR/.claude/skills/
cat $CLAUDE_CC_DIR/.claude/skills/commit/SKILL.md
cat $CLAUDE_CC_DIR/.claude/skills/firecrawl-scrape/SKILL.md
```
2 changes: 1 addition & 1 deletion .claude/skills/tldr-stats/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Show a beautiful dashboard with token usage, actual API costs, TLDR savings, and

1. Run the stats script:
```bash
python3 $CLAUDE_PROJECT_DIR/.claude/scripts/tldr_stats.py
python3 $CLAUDE_CC_DIR/.claude/scripts/tldr_stats.py
```

2. **Copy the full output into your response** so the user sees the dashboard directly in the chat. Do not just run the command silently - the user wants to see the stats.
Expand Down
25 changes: 19 additions & 6 deletions opc/scripts/setup/wizard.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -836,8 +836,10 @@ async def run_setup_wizard() -> None:
else:
console.print(" Skipped integration installation")

# Set CLAUDE_OPC_DIR environment variable for skills to find scripts
console.print(" Setting CLAUDE_OPC_DIR environment variable...")
# Set CLAUDE_OPC_DIR and CLAUDE_CC_DIR environment variables
# CLAUDE_OPC_DIR = opc/ directory (Python scripts, MCP runtime)
# CLAUDE_CC_DIR = repository root (contains .claude/scripts/, .claude/skills/)
console.print(" Setting environment variables...")
shell_config = None
shell = os.environ.get("SHELL", "")
if "zsh" in shell:
Expand All @@ -846,21 +848,32 @@ async def run_setup_wizard() -> None:
shell_config = Path.home() / ".bashrc"

opc_dir = _project_root # Use script location, not cwd (robust if invoked from elsewhere)
cc_dir = opc_dir.parent # Repository root (Continuous-Claude-v3/)
if shell_config and shell_config.exists():
content = shell_config.read_text()
export_line = f'export CLAUDE_OPC_DIR="{opc_dir}"'
changed = False
export_opc = f'export CLAUDE_OPC_DIR="{opc_dir}"'
export_cc = f'export CLAUDE_CC_DIR="{cc_dir}"'
if "CLAUDE_OPC_DIR" not in content:
with open(shell_config, "a") as f:
f.write(f"\n# Continuous-Claude OPC directory (for skills to find scripts)\n{export_line}\n")
console.print(f" [green]OK[/green] Added CLAUDE_OPC_DIR to {shell_config.name}")
f.write(f"\n# Continuous-Claude directories (for skills to find scripts)\n{export_opc}\n{export_cc}\n")
changed = True
elif "CLAUDE_CC_DIR" not in content:
with open(shell_config, "a") as f:
f.write(f"\n# Continuous-Claude root directory\n{export_cc}\n")
changed = True
if changed:
console.print(f" [green]OK[/green] Added CLAUDE_OPC_DIR and CLAUDE_CC_DIR to {shell_config.name}")
else:
console.print(f" [dim]CLAUDE_OPC_DIR already in {shell_config.name}[/dim]")
console.print(f" [dim]CLAUDE_OPC_DIR and CLAUDE_CC_DIR already in {shell_config.name}[/dim]")
elif sys.platform == "win32":
console.print(" [yellow]NOTE[/yellow] Add to your environment:")
console.print(f' set CLAUDE_OPC_DIR="{opc_dir}"')
console.print(f' set CLAUDE_CC_DIR="{cc_dir}"')
Comment on lines 870 to +872
Copy link
Copy Markdown

@sentry sentry bot Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The setup wizard provides set command instructions for Windows, which is incorrect for PowerShell users and will cause environment variables not to be set correctly.
Severity: MEDIUM

Suggested Fix

Detect if the user is on Windows and provide PowerShell-specific instructions using $env:VARIABLE="value" for session variables and [Environment]::SetEnvironmentVariable("VARIABLE", "value", "User") for persistent variables. Alternatively, the script could provide instructions for both cmd.exe and PowerShell.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: opc/scripts/setup/wizard.py#L870-L872

Potential issue: The setup wizard prints instructions for setting environment variables
on Windows using the `set VARIABLE="value"` syntax. This is valid for `cmd.exe` but not
for PowerShell, which is a recommended shell for Windows users. In PowerShell, `set` is
an alias for `Set-Variable`, which only sets a session-local variable, not a persistent
environment variable. Consequently, when a PowerShell user follows these instructions,
the `CLAUDE_OPC_DIR` and `CLAUDE_CC_DIR` variables will not be available in subsequent
sessions or processes, causing skills that rely on these paths to fail at runtime.

Did we get this right? 👍 / 👎 to inform future reviews.

else:
console.print(" [yellow]NOTE[/yellow] Add to your shell config:")
console.print(f' export CLAUDE_OPC_DIR="{opc_dir}"')
console.print(f' export CLAUDE_CC_DIR="{cc_dir}"')

# Step 8: Math Features (Optional)
console.print("\n[bold]Step 9/13: Math Features (Optional)[/bold]")
Expand Down