Name: scan-contexts
Author: xkazm04

Prompt file imported from xkazm04/dollar (.claude/commands/scan-contexts.md). Copyright stays with the author.

Context Scan and Generation

Your Mission

Analyze the Dollar codebase at C:\Users\kazda\kiro\dollar and create/update intelligent, structure-based contexts in the SQLite database.

Project Information

Project ID: 4b59804e-5a81-462f-85de-318ec55082ea
Project Name: Dollar
Project Path: C:\Users\kazda\kiro\dollar
Project Type: nextjs
Scan Timestamp: 2025-12-03T11-57-17

How to Complete This Task

Use the Claude Code skill for detailed instructions:

/context-scan-nextjs

This skill provides comprehensive guidance on:

Checking existing contexts
Mapping project structure
Creating properly-sized contexts
Using the required description template
Updating existing contexts
Quality validation

Quick Reference

Always replace these placeholders:

PROJECT_ID → 4b59804e-5a81-462f-85de-318ec55082ea
PROJECT_PATH → C:\Users\kazda\kiro\dollar

Essential Steps

1. Check Existing Contexts

curl -X GET "http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea"

2. Map Project Structure

# List all structural folders
find "C:\Users\kazda\kiro\dollar/src/app" -maxdepth 1 -type d -name "*-page" 2>/dev/null
find "C:\Users\kazda\kiro\dollar/src/app/features" -maxdepth 1 -type d -name "sub_*" 2>/dev/null

3. Read High-Level Architecture (Optional)

cat "C:\Users\kazda\kiro\dollar/context/high.md" 2>/dev/null || echo "No high-level architecture file found"

4. Create and Store Contexts

Follow the skill instructions to create contexts using the API.

5. Generate Markdown Report (MANDATORY)

After storing contexts in the database, you MUST create a summary report for debugging:

# Create docs/contexts directory
mkdir -p "C:\Users\kazda\kiro\dollar/docs/contexts"

# Generate the report
cat > "C:\Users\kazda\kiro\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md" << 'EOF'
# Context Scan Report

**Date**: 2025-12-03T11-57-17
**Project**: Dollar
**Project ID**: 4b59804e-5a81-462f-85de-318ec55082ea

## Execution Summary

| Metric | Value |
|--------|-------|
| Total Contexts | X |
| New Contexts Created | Y |
| Existing Contexts Updated | Z |
| Contexts Deleted | W |
| Total Files Covered | N |
| Coverage Percentage | M% |

## Created Contexts

| # | Context Name | Files | Database Status |
|---|--------------|-------|-----------------|
| 1 | Goals Page | 12 | ✓ Stored (ID: ctx_xxx) |
| 2 | Auth Module | 8 | ✓ Stored (ID: ctx_yyy) |

## Updated Contexts

| # | Context Name | Changes | Database Status |
|---|--------------|---------|-----------------|
| 1 | Project Dashboard | Added 2 files, removed 1 file | ✓ Updated |

## Deleted Contexts

| # | Context Name | Reason |
|---|--------------|--------|
| 1 | Old Feature | Feature removed from codebase |

## Detailed Context Information

### 1. Goals Page (12 files)
- **ID**: ctx_xxx
- **Status**: Created
- **Files**:
  - src/app/goals-page/page.tsx
  - src/app/goals-page/GoalsList.tsx
  - [... list all files ...]
- **Description Preview**: Overview of goals management feature...

### 2. Auth Module (8 files)
- **ID**: ctx_yyy
- **Status**: Created
- **Files**:
  - src/app/features/sub_auth/Login.tsx
  - [... list all files ...]

[Continue for all contexts...]

## Files Not Included in Any Context

- src/temp/test-file.ts (temporary test file)
- src/deprecated/old-component.tsx (deprecated)

## Verification

To verify contexts were saved:
```bash
curl -X GET "http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea"

Issues and Warnings

⚠️ Context "X" has 22 files (recommended: 10-20)
✓ All contexts follow description template
✓ No duplicate files across contexts

Next Steps

Review generated contexts in the UI
Create context groups for better organization
Link related goals to contexts
Add preview images where applicable EOF


**This report is critical for debugging. It helps identify:**
- Contexts that were identified but not actually saved
- API errors during context creation
- Size and structure issues
- Coverage gaps

## Final Output

After completing all steps and generating the markdown report:

1. Confirm all contexts were stored in the database
2. Provide a brief summary in your response
3. Mention the location of the detailed report

Example final message:

Context scan complete!

Created 8 new contexts and updated 3 existing ones. Total coverage: 156 files (87% of codebase)

Detailed report saved to: C:\Users\kazda\kiro\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md

All contexts verified in database.


## Important Notes

- Use the `/context-scan-nextjs` skill for comprehensive guidance
- Generate the markdown report AFTER storing contexts (helps debug save issues)
- Follow the exact description template for consistency
- Respect folder boundaries to keep contexts manageable
- Update existing contexts when possible instead of creating duplicates

Install scan-contexts and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Context Scan and Generation ## Your Mission Analyze the **Dollar** codebase at **C:\Users\kazda\kiro\dollar** and create/update intelligent, structure-based contexts in the SQLite database. ## Project Information - **Project ID**: 4b59804e-5a81-462f-85de-318ec55082ea - **Project Name**: Dollar - **Project Path**: C:\Users\kazda\kiro\dollar - **Project Type**: nextjs - **Scan Timestamp**: 2025-12-03T11-57-17 ## How to Complete This Task Use the Claude Code skill for detailed instructions: ``` /context-scan-nextjs ``` This skill provides comprehensive guidance on: - Checking existing contexts - Mapping project structure - Creating properly-sized contexts - Using the required description template - Updating existing contexts - Quality validation ## Quick Reference **Always replace these placeholders:** - `PROJECT_ID` → 4b59804e-5a81-462f-85de-318ec55082ea - `PROJECT_PATH` → C:\Users\kazda\kiro\dollar ## Essential Steps ### 1. Check Existing Contexts ```bash curl -X GET "http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea" ``` ### 2. Map Project Structure ```bash # List all structural folders find "C:\Users\kazda\kiro\dollar/src/app" -maxdepth 1 -type d -name "*-page" 2>/dev/null find "C:\Users\kazda\kiro\dollar/src/app/features" -maxdepth 1 -type d -name "sub_*" 2>/dev/null ``` ### 3. Read High-Level Architecture (Optional) ```bash cat "C:\Users\kazda\kiro\dollar/context/high.md" 2>/dev/null || echo "No high-level architecture file found" ``` ### 4. Create and Store Contexts Follow the skill instructions to create contexts using the API. ### 5. Generate Markdown Report (MANDATORY) **After storing contexts in the database, you MUST create a summary report for debugging:** ```bash # Create docs/contexts directory mkdir -p "C:\Users\kazda\kiro\dollar/docs/contexts" # Generate the report cat > "C:\Users\kazda\kiro\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md" << 'EOF' # Context Scan Report **Date**: 2025-12-03T11-57-17 **Project**: Dollar **Project ID**: 4b59804e-5a81-462f-85de-318ec55082ea ## Execution Summary | Metric | Value | |--------|-------| | Total Contexts | X | | New Contexts Created | Y | | Existing Contexts Updated | Z | | Contexts Deleted | W | | Total Files Covered | N | | Coverage Percentage | M% | ## Created Contexts | # | Context Name | Files | Database Status | |---|--------------|-------|-----------------| | 1 | Goals Page | 12 | ✓ Stored (ID: ctx_xxx) | | 2 | Auth Module | 8 | ✓ Stored (ID: ctx_yyy) | ## Updated Contexts | # | Context Name | Changes | Database Status | |---|--------------|---------|-----------------| | 1 | Project Dashboard | Added 2 files, removed 1 file | ✓ Updated | ## Deleted Contexts | # | Context Name | Reason | |---|--------------|--------| | 1 | Old Feature | Feature removed from codebase | ## Detailed Context Information ### 1. Goals Page (12 files) - **ID**: ctx_xxx - **Status**: Created - **Files**: - src/app/goals-page/page.tsx - src/app/goals-page/GoalsList.tsx - [... list all files ...] - **Description Preview**: Overview of goals management feature... ### 2. Auth Module (8 files) - **ID**: ctx_yyy - **Status**: Created - **Files**: - src/app/features/sub_auth/Login.tsx - [... list all files ...] [Continue for all contexts...] ## Files Not Included in Any Context - src/temp/test-file.ts (temporary test file) - src/deprecated/old-component.tsx (deprecated) ## Verification To verify contexts were saved: ```bash curl -X GET "http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea" ``` ## Issues and Warnings - ⚠️ Context "X" has 22 files (recommended: 10-20) - ✓ All contexts follow description template - ✓ No duplicate files across contexts ## Next Steps - [ ] Review generated contexts in the UI - [ ] Create context groups for better organization - [ ] Link related goals to contexts - [ ] Add preview images where applicable EOF ``` **This report is critical for debugging. It helps identify:** - Contexts that were identified but not actually saved - API errors during context creation - Size and structure issues - Coverage gaps ## Final Output After completing all steps and generating the markdown report: 1. Confirm all contexts were stored in the database 2. Provide a brief summary in your response 3. Mention the location of the detailed report Example final message: ``` Context scan complete! Created 8 new contexts and updated 3 existing ones. Total coverage: 156 files (87% of codebase) Detailed report saved to: C:\Users\kazda\kiro\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md All contexts verified in database. ``` ## Important Notes - Use the `/context-scan-nextjs` skill for comprehensive guidance - Generate the markdown report AFTER storing contexts (helps debug save issues) - Follow the exact description template for consistency - Respect folder boundaries to keep contexts manageable - Update existing contexts when possible instead of creating duplicates

{ "prompt": "# Context Scan and Generation\n\n## Your Mission\n\nAnalyze the **Dollar** codebase at **C:\\Users\\kazda\\kiro\\dollar** and create/update intelligent, structure-based contexts in the SQLite database.\n\n## Project Information\n\n- **Project ID**: 4b59804e-5a81-462f-85de-318ec55082ea\n- **Project Name**: Dollar\n- **Project Path**: C:\\Users\\kazda\\kiro\\dollar\n- **Project Type**: nextjs\n- **Scan Timestamp**: 2025-12-03T11-57-17\n\n## How to Complete This Task\n\nUse the Claude Code skill for detailed instructions:\n\n```\n/context-scan-nextjs\n```\n\nThis skill provides comprehensive guidance on:\n- Checking existing contexts\n- Mapping project structure\n- Creating properly-sized contexts\n- Using the required description template\n- Updating existing contexts\n- Quality validation\n\n## Quick Reference\n\n**Always replace these placeholders:**\n- `PROJECT_ID` → 4b59804e-5a81-462f-85de-318ec55082ea\n- `PROJECT_PATH` → C:\\Users\\kazda\\kiro\\dollar\n\n## Essential Steps\n\n### 1. Check Existing Contexts\n\n```bash\ncurl -X GET \"http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea\"\n```\n\n### 2. Map Project Structure\n\n```bash\n# List all structural folders\nfind \"C:\\Users\\kazda\\kiro\\dollar/src/app\" -maxdepth 1 -type d -name \"*-page\" 2>/dev/null\nfind \"C:\\Users\\kazda\\kiro\\dollar/src/app/features\" -maxdepth 1 -type d -name \"sub_*\" 2>/dev/null\n```\n\n### 3. Read High-Level Architecture (Optional)\n\n```bash\ncat \"C:\\Users\\kazda\\kiro\\dollar/context/high.md\" 2>/dev/null || echo \"No high-level architecture file found\"\n```\n\n### 4. Create and Store Contexts\n\nFollow the skill instructions to create contexts using the API.\n\n### 5. Generate Markdown Report (MANDATORY)\n\n**After storing contexts in the database, you MUST create a summary report for debugging:**\n\n```bash\n# Create docs/contexts directory\nmkdir -p \"C:\\Users\\kazda\\kiro\\dollar/docs/contexts\"\n\n# Generate the report\ncat > \"C:\\Users\\kazda\\kiro\\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md\" << 'EOF'\n# Context Scan Report\n\n**Date**: 2025-12-03T11-57-17\n**Project**: Dollar\n**Project ID**: 4b59804e-5a81-462f-85de-318ec55082ea\n\n## Execution Summary\n\n| Metric | Value |\n|--------|-------|\n| Total Contexts | X |\n| New Contexts Created | Y |\n| Existing Contexts Updated | Z |\n| Contexts Deleted | W |\n| Total Files Covered | N |\n| Coverage Percentage | M% |\n\n## Created Contexts\n\n| # | Context Name | Files | Database Status |\n|---|--------------|-------|-----------------|\n| 1 | Goals Page | 12 | ✓ Stored (ID: ctx_xxx) |\n| 2 | Auth Module | 8 | ✓ Stored (ID: ctx_yyy) |\n\n## Updated Contexts\n\n| # | Context Name | Changes | Database Status |\n|---|--------------|---------|-----------------|\n| 1 | Project Dashboard | Added 2 files, removed 1 file | ✓ Updated |\n\n## Deleted Contexts\n\n| # | Context Name | Reason |\n|---|--------------|--------|\n| 1 | Old Feature | Feature removed from codebase |\n\n## Detailed Context Information\n\n### 1. Goals Page (12 files)\n- **ID**: ctx_xxx\n- **Status**: Created\n- **Files**:\n - src/app/goals-page/page.tsx\n - src/app/goals-page/GoalsList.tsx\n - [... list all files ...]\n- **Description Preview**: Overview of goals management feature...\n\n### 2. Auth Module (8 files)\n- **ID**: ctx_yyy\n- **Status**: Created\n- **Files**:\n - src/app/features/sub_auth/Login.tsx\n - [... list all files ...]\n\n[Continue for all contexts...]\n\n## Files Not Included in Any Context\n\n- src/temp/test-file.ts (temporary test file)\n- src/deprecated/old-component.tsx (deprecated)\n\n## Verification\n\nTo verify contexts were saved:\n```bash\ncurl -X GET \"http://localhost:3000/api/contexts?projectId=4b59804e-5a81-462f-85de-318ec55082ea\"\n```\n\n## Issues and Warnings\n\n- ⚠️ Context \"X\" has 22 files (recommended: 10-20)\n- ✓ All contexts follow description template\n- ✓ No duplicate files across contexts\n\n## Next Steps\n\n- [ ] Review generated contexts in the UI\n- [ ] Create context groups for better organization\n- [ ] Link related goals to contexts\n- [ ] Add preview images where applicable\nEOF\n```\n\n**This report is critical for debugging. It helps identify:**\n- Contexts that were identified but not actually saved\n- API errors during context creation\n- Size and structure issues\n- Coverage gaps\n\n## Final Output\n\nAfter completing all steps and generating the markdown report:\n\n1. Confirm all contexts were stored in the database\n2. Provide a brief summary in your response\n3. Mention the location of the detailed report\n\nExample final message:\n\n```\nContext scan complete!\n\nCreated 8 new contexts and updated 3 existing ones.\nTotal coverage: 156 files (87% of codebase)\n\nDetailed report saved to:\nC:\\Users\\kazda\\kiro\\dollar/docs/contexts/scan-report-2025-12-03T11-57-17.md\n\nAll contexts verified in database.\n```\n\n## Important Notes\n\n- Use the `/context-scan-nextjs` skill for comprehensive guidance\n- Generate the markdown report AFTER storing contexts (helps debug save issues)\n- Follow the exact description template for consistency\n- Respect folder boundaries to keep contexts manageable\n- Update existing contexts when possible instead of creating duplicates", "variables": [], "notes": "Analyze the **Dollar** codebase at **C:\\Users\\kazda\\kiro\\dollar** and create/update intelligent, structure-based contexts in the SQLite database.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/xkazm04/dollar", "path": ".claude/commands/scan-contexts.md", "ref": "c5e48139941dfebde5361fa854dcd728489cfbe1", "url": "https://github.com/xkazm04/dollar/blob/c5e48139941dfebde5361fa854dcd728489cfbe1/.claude/commands/scan-contexts.md", "key": "xkazm04/dollar/.claude/commands/scan-contexts.md" } } }

scan-contexts

About