Skip to content

Conversation

@davila7
Copy link
Owner

@davila7 davila7 commented Jan 8, 2026

Added three comprehensive skills for working with Obsidian vault files:

  • obsidian-markdown: Create and edit Obsidian Flavored Markdown with wikilinks,
    embeds, callouts, properties, and other Obsidian-specific syntax
  • obsidian-bases: Create and edit Obsidian Bases (.base files) with views,
    filters, formulas, and database-like functionality
  • json-canvas: Create and edit JSON Canvas files (.canvas) with nodes, edges,
    groups, and connections for visual canvases and mind maps

These skills enable Claude Code to work seamlessly with Obsidian vaults,
including creating notes, managing databases, and building visual canvases.

Source: https://github.com/kepano/obsidian-skills
Author: Steph Ango (https://stephango.com/)
License: MIT


Summary by cubic

Adds three Obsidian document-processing skills for Markdown, Bases, and JSON Canvas, enabling full create/edit support for .md, .base, and .canvas files in Obsidian vaults. Also registers these skills in docs/components.json.

  • New Features
    • obsidian-markdown: Obsidian Flavored Markdown (wikilinks, embeds, callouts, properties).
    • obsidian-bases: Bases views, filters, formulas, summaries.
    • json-canvas: Canvas nodes, edges, groups, connections.

Written for commit 72d1a1b. Summary will update on new commits.

Added three comprehensive skills for working with Obsidian vault files:

- obsidian-markdown: Create and edit Obsidian Flavored Markdown with wikilinks,
  embeds, callouts, properties, and other Obsidian-specific syntax
- obsidian-bases: Create and edit Obsidian Bases (.base files) with views,
  filters, formulas, and database-like functionality
- json-canvas: Create and edit JSON Canvas files (.canvas) with nodes, edges,
  groups, and connections for visual canvases and mind maps

These skills enable Claude Code to work seamlessly with Obsidian vaults,
including creating notes, managing databases, and building visual canvases.

Source: https://github.com/kepano/obsidian-skills
Author: Steph Ango (https://stephango.com/)
License: MIT
@vercel
Copy link

vercel bot commented Jan 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docu Ready Ready Preview Jan 8, 2026 1:40pm

@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

⚠️ Security Audit Report

Status: ❌ FAILED

Summary

  • Total components: 383
  • Passed: 133
  • Failed: 250
  • ⚠️ Warnings: 178

❌ Failed Components

components/agents/ai-specialists/prompt-engineer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    semantic: 1 error(s)

    • SEM_E002: Prompt injection detected: Reference to system/developer instructions

components/agents/ai-specialists/search-specialist.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: tools

components/agents/blockchain-web3/smart-contract-auditor.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:193)

1 | ...
2 | ... security assessments. Examples: Context: User needs t ...
-----------------------------------------^
3 | ...

components/agents/blockchain-web3/smart-contract-specialist.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:200)

1 | ...
2 | ... ure contract patterns. Examples: Context: User needs t ...
-----------------------------------------^
3 | ...

components/agents/blockchain-web3/web3-integration-specialist.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:237)

1 | ...
2 | ... and dApp development. Examples: Context: User needs t ...
-----------------------------------------^
3 | ...

components/agents/business-marketing/cli-tool/components/agents/business-marketing/cli-tool/components/agents/business-marketing/vital-health-content-agent.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/agents/business-marketing/cli-tool/components/agents/business-marketing/vital-health-content-agent.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/agents/database/database-architect.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E011: Hardcoded password detected

components/agents/database/neon-auth-specialist.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    semantic: 1 error(s)

    • SEM_E017: Inline event handler detected (XSS risk)

components/agents/database/neon-expert.md

  • Errors: 2

  • Warnings: 1

  • Score: 89/100

    semantic: 2 error(s)

    • SEM_E011: Hardcoded password detected
    • SEM_E017: Inline event handler detected (XSS risk)

components/agents/deep-research-team/agent-overview.md

  • Errors: 2

  • Warnings: 1

  • Score: 89/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E002: Prompt injection detected: Reference to system/developer instructions

components/agents/deep-research-team/data-analyst.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:425)

1 | ...
2 | ...
3 | ...
4 | ... amples:\n- \n Context: The user wants to understand m ...
-----------------------------------------^

components/agents/deep-research-team/query-clarifier.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:285)

1 | ...
2 | ...
3 | ...
4 | ... ecific and actionable. Examples: Context: The user has ...
-----------------------------------------^

components/agents/deep-research-team/report-generator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:426)

1 | ...
2 | ...
3 | ...
4 | ... the research process. Examples: Context: The user has ...
-----------------------------------------^

components/agents/deep-research-team/research-brief-generator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:353)

1 | ...
2 | ...
3 | ...
4 | ... cess criteria. Context: The user has asked a research ...
-----------------------------------------^

components/agents/deep-research-team/research-coordinator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:307)

1 | ...
2 | ...
3 | ...
4 | ... sive coverage. Context: The user has asked for a compr ...
-----------------------------------------^

components/agents/deep-research-team/research-orchestrator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:283)

1 | ...
2 | ...
3 | ...
4 | ... rt generation. Context: User wants to conduct thorough ...
-----------------------------------------^

components/agents/deep-research-team/research-synthesizer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:458)

1 | ...
2 | ...
3 | ...
4 | ... nd actionable. Context: The user has multiple research ...
-----------------------------------------^

components/agents/deep-research-team/technical-researcher.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (4:358)

1 | ...
2 | ...
3 | ...
4 | ... plementations. Context: The user wants to understand d ...
-----------------------------------------^

components/agents/development-team/devops-engineer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E011: Hardcoded password detected

components/agents/development-team/fullstack-developer.md

  • Errors: 2

  • Warnings: 2

  • Score: 88/100

    semantic: 2 error(s)

    • SEM_E011: Hardcoded password detected
    • SEM_E017: Inline event handler detected (XSS risk)

components/agents/development-tools/command-expert.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E007: Security bypass attempt detected

components/agents/development-tools/context-manager.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E005: Credential harvesting pattern detected

components/agents/development-tools/test-engineer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E011: Hardcoded password detected

components/agents/development-tools/unused-code-cleaner.md

  • Errors: 2

  • Warnings: 1

  • Score: 89/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E016: javascript: protocol detected (XSS risk)

components/agents/expert-advisors/agent-expert.md

  • Errors: 1

  • Warnings: 3

  • Score: 92/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: tools

components/agents/expert-advisors/architect-review.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:167)

1 | ...
2 | ... , and maintainability. Examples: Context: A developer ...
-----------------------------------------^
3 | ...
4 | ...

components/agents/expert-advisors/dependency-manager.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:153)

1 | ...
2 | ... nd license compliance. Examples: Context: A user wants ...
-----------------------------------------^
3 | ...

components/agents/expert-advisors/documentation-expert.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:192)

1 | ...
2 | ... cumentation from code. Examples: Context: A user wants ...
-----------------------------------------^
3 | ...

components/agents/mcp-dev-team/mcp-security-auditor.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    semantic: 1 error(s)

    • SEM_E007: Security bypass attempt detected

components/agents/mcp-dev-team/mcp-testing-engineer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    semantic: 1 error(s)

    • SEM_E007: Security bypass attempt detected

components/agents/podcast-creator-team/academic-research-synthesizer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E005: Credential harvesting pattern detected

components/agents/podcast-creator-team/seo-podcast-optimizer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    semantic: 1 error(s)

    • SEM_E005: Credential harvesting pattern detected

components/commands/automation/act.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/automation/ci-pipeline.md

  • Errors: 1

  • Warnings: 3

  • Score: 92/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [pipeline-name] | setup | status | fix
------------------------------------^
3 | description: Manage and automate CI/CD pipeline configuration w ...

components/commands/automation/husky.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Bash, Read
2 | argument-hint: [--skip-install] | [--only-lint] | [--skip-tests]
-------------------------------------^
3 | description: Run comprehensive CI checks and fix issues until re ...

components/commands/automation/workflow-orchestrator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [workflow-name] | create | run | schedule | monitor
------------------------------------^
3 | description: Orchestrate complex automation workflows with task ...

components/commands/database/supabase-backup-manager.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [operation] | --backup | --restore | --sched ...
--------------------------------^
3 | description: Manage Supabase database backups with automate ...

components/commands/database/supabase-data-explorer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [table-name] | --query [sql] | --export | --i ...
---------------------------------^
3 | description: Explore and analyze Supabase database data with ...

components/commands/database/supabase-migration-assistant.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [migration-type] | --create | --alter | --seed | ...
-------------------------------------^
3 | description: Generate and manage Supabase database migrations wi ...

components/commands/database/supabase-performance-optimizer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:36)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [optimization-type] | --queries | --indexes | --stor ...
----------------------------------------^
3 | description: Optimize Supabase database performance with intelligen ...

components/commands/database/supabase-realtime-monitor.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [monitoring-type] | --connections | --subscription ...
--------------------------------------^
3 | description: Monitor and optimize Supabase realtime connections w ...

components/commands/database/supabase-schema-sync.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [action] | --pull | --push | --diff | --v ...
-----------------------------^
3 | description: Synchronize database schema with Supabase u ...

components/commands/database/supabase-security-audit.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [audit-scope] | --rls | --permissions | --auth ...
----------------------------------^
3 | description: Conduct comprehensive Supabase security audit wi ...

components/commands/database/supabase-type-generator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [generation-scope] | --all-tables | --specific-tabl ...
---------------------------------------^
3 | description: Generate TypeScript types from Supabase schema with a ...

components/commands/deployment/add-changelog.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:26)

1 | allowed-tools: Read, Edit, Write, Bash
2 | argument-hint: [version] | [entry-type] [description]
------------------------------^
3 | description: Generate and maintain project changelog with ...

components/commands/deployment/blue-green-deployment.md

  • Errors: 1

  • Warnings: 12

  • Score: 83/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [strategy] | setup | deploy | switch | roll ...
-------------------------------^
3 | description: Implement blue-green deployment strategy with ...

components/commands/deployment/changelog-demo-command.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [format] | --generate | --validate | --demo
-----------------------------^
3 | description: Demonstrate changelog automation features w ...

components/commands/deployment/ci-setup.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [platform] | --github-actions | --gitlab-ci ...
-------------------------------^
3 | description: Setup comprehensive CI/CD pipeline with autom ...

components/commands/deployment/containerize-application.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [application-type] | --node | --python | --java | - ...
---------------------------------------^
3 | description: Containerize application with optimized Docker config ...

components/commands/deployment/deployment-monitoring.md

  • Errors: 2

  • Warnings: 12

  • Score: 78/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [monitoring-type] | setup | dashboard | alerts | m ...
--------------------------------------^
3 | description: Comprehensive deployment monitoring with observabili ...
semantic: 1 error(s)

  • SEM_E011: Hardcoded password detected

components/commands/deployment/hotfix-deploy.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Edit, Bash
2 | argument-hint: [hotfix-type] | --security | --critical | --ro ...
----------------------------------^
3 | description: Deploy critical hotfixes with emergency procedur ...

components/commands/deployment/prepare-release.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [version-type] | patch | minor | major | --pre- ...
-----------------------------------^
3 | description: Prepare and validate release packages with compre ...

components/commands/deployment/rollback-deploy.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Edit, Bash
2 | argument-hint: [target-version] | --previous | --emergency | --v ...
-------------------------------------^
3 | description: Rollback deployment to previous version with safety ...

components/commands/deployment/setup-automated-releases.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [release-type] | --semantic | --conventional-co ...
-----------------------------------^
3 | description: Setup automated release workflows with semantic v ...

components/commands/deployment/setup-kubernetes-deployment.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [deployment-type] | --microservices | --monolith | ...
--------------------------------------^
3 | description: Configure comprehensive Kubernetes deployment with m ...

components/commands/documentation/create-architecture-documentation.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/documentation/create-onboarding-guide.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [role-type] | --developer | --designer | --d ...
--------------------------------^
3 | description: Create comprehensive developer onboarding guid ...

components/commands/documentation/doc-api.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [api-type] | --openapi | --graphql | --rest ...
-------------------------------^
3 | description: Generate comprehensive API documentation from ...
semantic: 1 error(s)

  • SEM_E014: <script> tag detected (XSS risk)

components/commands/documentation/docs-maintenance.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash, Grep
2 | argument-hint: [maintenance-type] | --audit | --update | --validat ...
---------------------------------------^
3 | description: Use PROACTIVELY to implement comprehensive documentat ...

components/commands/documentation/generate-api-documentation.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [output-format] | --swagger-ui | --redoc | --pos ...
------------------------------------^
3 | description: Auto-generate API reference documentation with mul ...

components/commands/documentation/interactive-documentation.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [platform] | --docusaurus | --gitbook | --n ...
-------------------------------^
3 | description: Use PROACTIVELY to create interactive documen ...

components/commands/documentation/load-llms-txt.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Bash, WebFetch
2 | argument-hint: [data-source] | --xatu | --custom-url | --validate
----------------------------------^
3 | description: Load and process external documentation context ...

components/commands/documentation/migration-guide.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [migration-type] | framework | database | cloud | ...
-------------------------------------^
3 | description: Create comprehensive migration guides with step-by- ...

components/commands/documentation/troubleshooting-guide.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [system-component] | --application | --database | - ...
---------------------------------------^
3 | description: Generate systematic troubleshooting documentation wit ...

components/commands/documentation/update-docs.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [doc-type] | --implementation | --api | --a ...
-------------------------------^
3 | description: Systematically update project documentation w ...

components/commands/game-development/game-analytics-integration.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [analytics-type] | --player-behavior | --performa ...
-------------------------------------^
3 | description: Use PROACTIVELY to implement game analytics systems ...

components/commands/game-development/game-asset-pipeline.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [pipeline-type] | --art | --audio | --models | - ...
------------------------------------^
3 | description: Use PROACTIVELY to build automated game asset proc ...

components/commands/game-development/game-performance-profiler.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [profile-type] | --fps | --memory | --rendering ...
-----------------------------------^
3 | description: Use PROACTIVELY to analyze game performance bottl ...

components/commands/game-development/game-testing-framework.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [test-type] | --unit | --integration | --per ...
--------------------------------^
3 | description: Use PROACTIVELY to implement comprehensive gam ...

components/commands/game-development/unity-project-setup.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [project-name] | --2d | --3d | --mobile | --vr ...
-----------------------------------^
3 | description: Use PROACTIVELY to set up professional Unity game ...

components/commands/git/feature.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/git/finish.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Bash(git:*), Read, Edit
2 | argument-hint: [--no-delete] [--no-tag]
----------------------------------^
3 | description: Complete and merge current Git Flow branch (feat ...

components/commands/git/flow-status.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/git/hotfix.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/git/release.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/git-workflow/branch-cleanup.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Bash(git branch:), Bash(git checkout:), Ba ...
2 | argument-hint: [--dry-run] | [--force] | [--remote-only] | ...
--------------------------------^
3 | description: Use PROACTIVELY to clean up merged branches, s ...

components/commands/git-workflow/commit.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:26)

1 | allowed-tools: Bash(git add:), Bash(git status:), Bash( ...
2 | argument-hint: [message] | --no-verify | --amend
------------------------------^
3 | description: Create well-formatted commits with conventio ...

components/commands/git-workflow/create-pr.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/git-workflow/create-pull-request.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/git-workflow/create-worktrees.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/git-workflow/fix-github-issue.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/git-workflow/gemini-review.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Bash(gh:*), Read, Grep, TodoWrite, Edit, Mul ...
2 | argument-hint: [pr-number] | --analyze-only | --preview | - ...
--------------------------------^
3 | description: Transform Gemini Code Assist PR reviews into p ...
4 | model: claude-sonnet-4-5-20250929

components/commands/git-workflow/git-bisect-helper.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Bash(git bisect:), Bash(git log:), Bash(git ...
2 | argument-hint: [good-commit] [bad-commit] | --auto [test-comm ...
----------------------------------^
3 | description: Use PROACTIVELY to guide automated git bisect se ...

components/commands/git-workflow/pr-review.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/git-workflow/update-branch-name.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/marketing/publisher-all.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/marketing/publisher-devto.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/marketing/publisher-linkedin.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name
      semantic: 1 error(s)
    • SEM_E005: Credential harvesting pattern detected

components/commands/marketing/publisher-medium.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/marketing/publisher-x.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/nextjs-vercel/nextjs-api-tester.md

  • Errors: 1

  • Warnings: 7

  • Score: 88/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [route-path] [--method=GET] [--data='{}'] [-- ...
---------------------------------^
3 | description: Test and validate Next.js API routes with compr ...

components/commands/nextjs-vercel/nextjs-bundle-analyzer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:26)

1 | allowed-tools: Read, Edit, Bash
2 | argument-hint: [--build] [--analyze] [--report]
------------------------------^
3 | description: Analyze and optimize Next.js bundle size wit ...

components/commands/nextjs-vercel/nextjs-component-generator.md

  • Errors: 2

  • Warnings: 1

  • Score: 89/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit
2 | argument-hint: [component-name] [--client] [--server] [--page] [ ...
-------------------------------------^
3 | description: Generate optimized React components for Next.js wit ...
semantic: 1 error(s)

  • SEM_E017: Inline event handler detected (XSS risk)

components/commands/nextjs-vercel/nextjs-middleware-creator.md

  • Errors: 2

  • Warnings: 5

  • Score: 85/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit
2 | argument-hint: [middleware-type] [--auth] [--rate-limit] [--redir ...
--------------------------------------^
3 | description: Create optimized Next.js middleware with authenticat ...
semantic: 1 error(s)

  • SEM_E005: Credential harvesting pattern detected

components/commands/nextjs-vercel/nextjs-migration-helper.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash, Grep, Glob
2 | argument-hint: [--pages-to-app] [--js-to-ts] [--class-to-hooks] ...
-------------------------------------^
3 | description: Comprehensive Next.js migration assistant for Pages ...

components/commands/nextjs-vercel/nextjs-performance-audit.md

  • Errors: 2

  • Warnings: 3

  • Score: 87/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Edit, Bash
2 | argument-hint: [--lighthouse] [--bundle] [--runtime] [--all]
-----------------------------------^
3 | description: Comprehensive Next.js performance audit with acti ...
semantic: 1 error(s)

  • SEM_E014: <script> tag detected (XSS risk)

components/commands/nextjs-vercel/nextjs-scaffold.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [project-name] [--typescript] [--tailwind] [--a ...
-----------------------------------^
3 | description: Create a new Next.js application with best practi ...

components/commands/nextjs-vercel/vercel-deploy-optimize.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [environment] [--analyze] [--preview]
----------------------------------^
3 | description: Optimize and deploy Next.js application to Verce ...

components/commands/nextjs-vercel/vercel-edge-function.md

  • Errors: 3

  • Warnings: 4

  • Score: 81/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit
2 | argument-hint: [function-name] [--auth] [--geo] [--transform] [ ...
------------------------------------^
3 | description: Generate optimized Vercel Edge Functions with geol ...
semantic: 2 error(s)

  • SEM_E005: Credential harvesting pattern detected
  • SEM_E011: Hardcoded password detected

components/commands/nextjs-vercel/vercel-env-sync.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [--pull] [--push] [--validate] [--backup]
-----------------------------^
3 | description: Synchronize environment variables between l ...

components/commands/orchestration/archive.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/commit.md

  • Errors: 1

  • Warnings: 2

  • Score: 93/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/find.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/log.md

  • Errors: 1

  • Warnings: 3

  • Score: 92/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/move.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/optimize.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/remove.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/report.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/resume.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/start.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/status.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/orchestration/sync.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/performance/add-performance-monitoring.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [monitoring-type] | --apm | --rum | --custom
--------------------------------------^
3 | description: Setup comprehensive application performance monitori ...

components/commands/performance/implement-caching-strategy.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [cache-type] | --browser | --application | -- ...
---------------------------------^
3 | description: Design and implement comprehensive caching solu ...

components/commands/performance/optimize-api-performance.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [api-type] | --rest | --graphql | --grpc
-------------------------------^
3 | description: Comprehensive API performance optimization wi ...

components/commands/performance/optimize-build.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/performance/optimize-bundle-size.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [build-tool] | --webpack | --vite | --rollup
---------------------------------^
3 | description: Reduce and optimize bundle sizes through analys ...

components/commands/performance/optimize-database-performance.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [database-type] | --postgresql | --mysql | --mongodb
------------------------------------^
3 | description: Optimize database queries, indexing, and performan ...

components/commands/performance/optimize-memory-usage.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [target-area] | --frontend | --backend | --dat ...
----------------------------------^
3 | description: Comprehensive memory usage optimization with lea ...

components/commands/performance/performance-audit.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [target-area] | --frontend | --backend | --full
----------------------------------^
3 | description: Comprehensive performance audit with metrics, bo ...

components/commands/performance/setup-cdn-optimization.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [cdn-provider] | --cloudflare | --aws | --fastly
-----------------------------------^
3 | description: Configure CDN for optimal content delivery, cachi ...

components/commands/performance/system-behavior-simulator.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/project-management/add-package.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash, Glob
2 | argument-hint: [package-name] [package-type] | --library | --a ...
-----------------------------------^
3 | description: Add and configure new package to workspace with p ...

components/commands/project-management/add-to-changelog.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:26)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [version] [change-type] [message] | --adde ...
------------------------------^
3 | description: Add entry to project changelog following Kee ...

components/commands/project-management/create-feature.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [feature-name] | [feature-type] [name]
-----------------------------------^
3 | description: Scaffold new feature with boilerplate code, tests ...

components/commands/project-management/create-jtbd.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Grep, Glob
2 | argument-hint: [feature-name] | --template | --interactive
-----------------------------------^
3 | description: Create Jobs-to-be-Done (JTBD) analysis for produc ...

components/commands/project-management/create-prd.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Grep, Glob
2 | argument-hint: [feature-name] | --template | --interactive
-----------------------------------^
3 | description: Create Product Requirements Document (PRD) for ne ...

components/commands/project-management/create-prp.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:38)

1 | ... d-tools: Read, Write, Edit, WebSearch, Grep, Glob
2 | ... nt-hint: [feature-description] | --research | --template | --va ...
-----------------------------------------^
3 | ... ption: Create comprehensive Product Requirement Prompt (PRP) wi ...

components/commands/project-management/init-project.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash, Glob
2 | argument-hint: [project-type] [framework] | --react | --vue | ...
-----------------------------------^
3 | description: Initialize new project with essential structure, ...

components/commands/project-management/milestone-tracker.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Bash, Read, Grep, Glob
2 | argument-hint: [time-period] | --sprint | --quarter | --all
----------------------------------^
3 | description: Track and analyze project milestone progress wit ...

components/commands/project-management/pac-configure.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [project-name] | --minimal | --epic-name | --owner
-----------------------------------^
3 | description: Initialize Product as Code (PAC) project structur ...

components/commands/project-management/pac-create-epic.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [epic-name] | --name | --description | --owner
--------------------------------^
3 | description: Create new PAC epic following Product as Code ...

components/commands/project-management/pac-create-ticket.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [ticket-name] | --epic | --type | --assignee | ...
----------------------------------^
3 | description: Create new PAC ticket within an epic following P ...

components/commands/project-management/pac-update-status.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [ticket-id] | --status | --assignee | --comment
--------------------------------^
3 | description: Update PAC ticket status and track progress in ...

components/commands/project-management/pac-validate.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Bash
2 | argument-hint: [scope] | --file | --epic | --fix | --pr ...
----------------------------^
3 | description: Validate Product as Code project structure ...

components/commands/project-management/project-health-check.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:36)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [evaluation-period] | --30-days | --sprint | --quarter
----------------------------------------^
3 | description: Analyze overall project health and generate comprehens ...

components/commands/project-management/project-timeline-simulator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [project-type] | --duration | --team-size | --r ...
-----------------------------------^
3 | description: Simulate project outcomes with variable modeling, ...

components/commands/project-management/project-to-linear.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:38)

1 | ... d-tools: Read, Bash, Grep, Glob
2 | ... nt-hint: [project-description] | --team-id | --create-new | --e ...
-----------------------------------------^
3 | ... ption: Sync project structure and requirements to Linear worksp ...

components/commands/project-management/release.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [version-type] | --patch | --minor | --major | ...
-----------------------------------^
3 | description: Prepare and execute project release with version ...

components/commands/project-management/todo.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit
2 | argument-hint: [action] [task-description] | add | compl ...
-----------------------------^
3 | description: Manage project todos in todos.md file

components/commands/security/add-authentication-system.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [auth-method] | --oauth | --jwt | --mfa | --pa ...
----------------------------------^
3 | description: Implement secure user authentication system with ...

components/commands/security/dependency-audit.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Bash, Grep
2 | argument-hint: [scope] | --security | --licenses | --up ...
----------------------------^
3 | description: Audit dependencies for security vulnerabil ...

components/commands/security/penetration-test.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [target] | --web-app | --api | --auth | - ...
-----------------------------^
3 | description: Perform penetration testing and vulnerabili ...

components/commands/security/secrets-scanner.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [scope] | --api-keys | --passwords | --c ...
----------------------------^
3 | description: Scan codebase for exposed secrets, credent ...

components/commands/security/security-audit.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [focus-area] | --full
---------------------------------^
3 | description: Perform comprehensive security assessment and v ...

components/commands/security/security-hardening.md

  • Errors: 1

  • Warnings: 2

  • Score: 93/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [focus-area] | --headers | --auth | --encrypt ...
---------------------------------^
3 | description: Harden application security configuration with ...

components/commands/setup/create-database-migrations.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [migration-name] | --create-table | --add-column ...
-------------------------------------^
3 | description: Create and manage database migrations with proper v ...

components/commands/setup/design-database-schema.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [schema-type] | --relational | --nosql | --hyb ...
----------------------------------^
3 | description: Design optimized database schemas with proper re ...

components/commands/setup/design-rest-api.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [api-version] | --v1 | --v2 | --graphql-hybrid ...
----------------------------------^
3 | description: Design RESTful API architecture with comprehensi ...

components/commands/setup/implement-graphql-api.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [schema-approach] | --schema-first | --code-first ...
--------------------------------------^
3 | description: Implement GraphQL API with comprehensive schema, res ...

components/commands/setup/migrate-to-typescript.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:37)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [migration-strategy] | --gradual | --complete | --str ...
-----------------------------------------^
3 | description: Migrate JavaScript project to TypeScript with proper ty ...

components/commands/setup/setup-ci-cd-pipeline.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [platform] | --github-actions | --gitlab-ci ...
-------------------------------^
3 | description: Setup comprehensive CI/CD pipeline with autom ...

components/commands/setup/setup-development-environment.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [environment-type] | --local | --docker | --cloud | ...
---------------------------------------^
3 | description: Setup comprehensive development environment with tool ...

components/commands/setup/setup-docker-containers.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [environment-type] | --development | --production | ...
---------------------------------------^
3 | description: Setup Docker containerization with multi-stage builds ...

components/commands/setup/setup-formatting.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [language] | --javascript | --typescript | ...
-------------------------------^
3 | description: Configure comprehensive code formatting tools ...

components/commands/setup/setup-linting.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [language] | --javascript | --typescript | ...
-------------------------------^
3 | description: Configure comprehensive code linting and qual ...

components/commands/setup/setup-monitoring-observability.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [monitoring-type] | --metrics | --logging | --trac ...
--------------------------------------^
3 | description: Setup comprehensive monitoring and observability wit ...

components/commands/setup/setup-monorepo.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [monorepo-tool] | --nx | --lerna | --rush | --tu ...
------------------------------------^
3 | description: Configure monorepo project structure with comprehe ...

components/commands/setup/setup-rate-limiting.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [rate-limit-type] | --api | --authentication | --f ...
--------------------------------------^
3 | description: Implement comprehensive API rate limiting with advan ...

components/commands/setup/update-dependencies.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [update-strategy] | --patch | --minor | --major | ...
--------------------------------------^
3 | description: Update and modernize project dependencies with compr ...

components/commands/setup/vercel-analytics.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

components/commands/simulation/business-scenario-explorer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [business-context] | --market-expansion | --product ...
---------------------------------------^
3 | description: Explore multiple business timeline scenarios with com ...

components/commands/simulation/constraint-modeler.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:36)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [constraint-domain] | --business | --technical | --r ...
----------------------------------------^
3 | description: Model system constraints with validation, dependency m ...

components/commands/simulation/decision-tree-explorer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [decision-context] | --strategic | --investment | - ...
---------------------------------------^
3 | description: Explore complex decision branches with probability an ...

components/commands/simulation/digital-twin-creator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [twin-subject] | --manufacturing | --business-p ...
-----------------------------------^
3 | description: Create calibrated digital twins with real-world v ...

components/commands/simulation/future-scenario-generator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [time-horizon] | --near-term | --medium-term | ...
-----------------------------------^
3 | description: Generate comprehensive future scenarios with plau ...

components/commands/simulation/market-response-modeler.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [market-trigger] | --product-launch | --pricing-c ...
-------------------------------------^
3 | description: Model comprehensive market and customer responses w ...

components/commands/simulation/monte-carlo-simulator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:36)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [simulation-target] | --financial-projections | --pr ...
----------------------------------------^
3 | description: Run Monte Carlo simulations with probability distribut ...

components/commands/simulation/simulation-calibrator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [simulation-type] | --business | --technical | --b ...
--------------------------------------^
3 | description: Calibrate simulation accuracy with systematic valida ...

components/commands/simulation/system-dynamics-modeler.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [system-type] | --business-ecosystem | --organ ...
----------------------------------^
3 | description: Model complex system dynamics with feedback loop ...

components/commands/simulation/timeline-compressor.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, WebSearch
2 | argument-hint: [timeline-type] | --product-development | --mark ...
------------------------------------^
3 | description: Compress real-world timelines into rapid simulatio ...

components/commands/svelte/svelte-a11y.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E017: Inline event handler detected (XSS risk)

components/commands/svelte/svelte-component.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit
2 | argument-hint: [component-name] [--typescript] [--story]
-------------------------------------^
3 | description: Create new Svelte components with best practices, T ...
semantic: 1 error(s)

  • SEM_E014: <script> tag detected (XSS risk)

components/commands/svelte/svelte-debug.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-migrate.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-optimize.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-scaffold.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-storybook-migrate.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E014: <script> tag detected (XSS risk)

components/commands/svelte/svelte-storybook-mock.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-storybook-setup.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-storybook-story.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E014: <script> tag detected (XSS risk)

components/commands/svelte/svelte-storybook-troubleshoot.md

  • Errors: 1

  • Warnings: 4

  • Score: 91/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-storybook.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-test-coverage.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-test-fix.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-test-setup.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/svelte/svelte-test.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/sync/bidirectional-sync.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [sync-mode] | --full | --incremental | --dry ...
--------------------------------^
3 | description: Enable comprehensive bidirectional GitHub-Line ...

components/commands/sync/bulk-import-issues.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [import-scope] | --state | --label | --mileston ...
-----------------------------------^
3 | description: Bulk import GitHub issues to Linear with comprehe ...

components/commands/sync/cross-reference-manager.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [action] | audit | repair | map | validat ...
-----------------------------^
3 | description: Manage cross-platform reference links betwe ...

components/commands/sync/issue-to-linear-task.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [issue-number] | --team | --project | --close-g ...
-----------------------------------^
3 | description: Convert individual GitHub issues to Linear tasks ...

components/commands/sync/linear-task-to-issue.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:26)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [task-id] | --repo | --milestone | --close ...
------------------------------^
3 | description: Convert Linear tasks to GitHub issues with r ...

components/commands/sync/sync-automation-setup.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [setup-mode] | --full | --webhooks-only | --m ...
---------------------------------^
3 | description: Setup comprehensive automated synchronization w ...

components/commands/sync/sync-conflict-resolver.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [action] | detect | resolve | analyze | c ...
-----------------------------^
3 | description: Resolve synchronization conflicts with inte ...

components/commands/sync/sync-health-monitor.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [scope] | --github | --linear | --webhoo ...
----------------------------^
3 | description: Monitor and diagnose GitHub-Linear sync he ...

components/commands/sync/sync-issues-to-linear.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [sync-scope] | --state | --label | --assignee ...
---------------------------------^
3 | description: Sync GitHub issues to Linear workspace with com ...

components/commands/sync/sync-linear-to-issues.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [sync-scope] | --team | --project | --priorit ...
---------------------------------^
3 | description: Sync Linear tasks to GitHub issues with state m ...

components/commands/sync/sync-migration-assistant.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:33)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [migration-type] | --github-to-linear | --linear- ...
-------------------------------------^
3 | description: Comprehensive migration assistant for large-scale G ...

components/commands/sync/sync-pr-to-task.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [pr-number] | --task | --auto-detect | --ena ...
--------------------------------^
3 | description: Link GitHub pull requests to Linear tasks with ...

components/commands/sync/sync-status.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Bash
2 | argument-hint: [--detailed] | [--health-check] | [--diagnostics]
---------------------------------^
3 | description: Monitor GitHub-Linear sync health status with p ...

components/commands/sync/task-from-pr.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [pr-number] | --team | --estimate | --batch- ...
--------------------------------^
3 | description: Create Linear tasks from GitHub pull requests ...

components/commands/team/architecture-review.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Glob, Grep, Bash
2 | argument-hint: [scope] | --modules | --patterns | --dep ...
----------------------------^
3 | description: Comprehensive architecture review with des ...

components/commands/team/decision-quality-analyzer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [analysis-type] | --bias-detection | --scenario- ...
------------------------------------^
3 | description: Analyze team decision quality with bias detection, ...

components/commands/team/dependency-mapper.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Glob, Grep, Bash
2 | argument-hint: [scope] | --tasks | --code | --circular ...
----------------------------^
3 | description: Map project and task dependencies with cri ...

components/commands/team/estimate-assistant.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:35)

1 | allowed-tools: Read, Bash, Glob, Grep
2 | argument-hint: [task-description] | --historical | --complexity-an ...
---------------------------------------^
3 | description: Generate accurate task estimates using historical dat ...

components/commands/team/issue-triage.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Write, Bash
2 | argument-hint: [scope] | --github-issues | --linear-tas ...
----------------------------^
3 | description: Intelligent issue triage with automatic ca ...

components/commands/team/memory-spring-cleaning.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Write, Edit, Glob
2 | argument-hint: [scope] | --claude-md | --documentation ...
----------------------------^
3 | description: Clean and organize project memory files wi ...

components/commands/team/migration-assistant.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [action] | --plan | --analyze | --migrate ...
-----------------------------^
3 | description: Comprehensive system migration assistance w ...

components/commands/team/retrospective-analyzer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:36)

1 | allowed-tools: Read, Write, Bash, Glob
2 | argument-hint: [sprint-identifier] | --metrics | --insights | --act ...
----------------------------------------^
3 | description: Analyze team retrospectives with quantitative metrics ...

components/commands/team/session-learning-capture.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Glob
2 | argument-hint: [capture-type] | --project-learnings | --implem ...
-----------------------------------^
3 | description: Capture and document session learnings with autom ...

components/commands/team/sprint-planning.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, WebSearch
2 | argument-hint: [sprint-duration] | [start-date] [duration]
--------------------------------------^
3 | description: Plan and organize sprint workflows with Linear integ ...

components/commands/team/standup-report.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:29)

1 | allowed-tools: Read, Bash, Glob, Grep
2 | argument-hint: [time-range] | --yesterday | --last-24h | --s ...
---------------------------------^
3 | description: Generate comprehensive daily standup reports wi ...

components/commands/team/team-knowledge-mapper.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Bash, Glob, Grep
2 | argument-hint: [mapping-type] | --skill-matrix | --knowledge-g ...
-----------------------------------^
3 | description: Map team knowledge and expertise with skill gap a ...

components/commands/team/team-velocity-tracker.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Bash, Glob, Grep
2 | argument-hint: [analysis-period] | --sprint | --monthly | --quart ...
--------------------------------------^
3 | description: Track and analyze team velocity with predictive fore ...

components/commands/team/team-workload-balancer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [analysis-type] | --current-workload | --skill-m ...
------------------------------------^
3 | description: Analyze and optimize team workload distribution wi ...

components/commands/testing/add-mutation-testing.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [language] | --javascript | --java | --pyth ...
-------------------------------^
3 | description: Setup comprehensive mutation testing with fra ...

components/commands/testing/add-property-based-testing.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:27)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [language] | --javascript | --python | --ja ...
-------------------------------^
3 | description: Implement property-based testing with framewo ...

components/commands/testing/e2e-setup.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [framework] | --cypress | --playwright | --w ...
--------------------------------^
3 | description: Configure comprehensive end-to-end testing sui ...

components/commands/testing/generate-test-cases.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:25)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [target] | [scope] | --unit | --integrati ...
-----------------------------^
3 | description: Generate comprehensive test cases with auto ...

components/commands/testing/generate-tests.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [file-path] | [component-name]
--------------------------------^
3 | description: Generate comprehensive test suite with unit, i ...

components/commands/testing/setup-comprehensive-testing.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:24)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [scope] | --unit | --integration | --e2e ...
----------------------------^
3 | description: Setup complete testing infrastructure with ...

components/commands/testing/setup-load-testing.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [testing-type] | --capacity | --stress | --spik ...
-----------------------------------^
3 | description: Configure comprehensive load testing with perform ...

components/commands/testing/setup-visual-testing.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [testing-scope] | --components | --pages | --res ...
------------------------------------^
3 | description: Setup comprehensive visual regression testing with ...

components/commands/testing/test-automation-orchestrator.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:37)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [orchestration-type] | --parallel | --sequential | -- ...
-----------------------------------------^
3 | description: Orchestrate comprehensive test automation with intellig ...

components/commands/testing/test-changelog-automation.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:34)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [automation-type] | --changelog | --workflow-demo ...
--------------------------------------^
3 | description: Automate changelog testing workflow with CI integrat ...

components/commands/testing/test-coverage.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [coverage-type] | --line | --branch | --function ...
------------------------------------^
3 | description: Analyze and improve test coverage with comprehensi ...

components/commands/testing/test-quality-analyzer.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:32)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [analysis-type] | --coverage-quality | --test-ef ...
------------------------------------^
3 | description: Analyze test suite quality with comprehensive metr ...

components/commands/testing/testing_plan_integration.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [target-code] | [test-type] | --rust | --inlin ...
----------------------------------^
3 | description: Create comprehensive integration testing plan wi ...

components/commands/testing/write-tests.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:30)

1 | allowed-tools: Read, Write, Edit, Bash
2 | argument-hint: [target-file] | [test-type] | --unit | --integ ...
----------------------------------^
3 | description: Write comprehensive unit and integration tests w ...

components/commands/utilities/all-tools.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E002: Prompt injection detected: Reference to system/developer instructions

components/commands/utilities/architecture-scenario-explorer.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/check-file.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/clean-branches.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/clean.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/cleanup-cache.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:31)

1 | allowed-tools: Bash(df:), Bash(du:), Bash(npm cache clean:*) ...
2 | argument-hint: [--aggressive] | [--maximum]
-----------------------------------^
3 | description: Clean system caches (npm, Homebrew, Yarn, browser ...

components/commands/utilities/code-permutation-tester.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/code-review.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E002: Invalid YAML syntax in frontmatter: bad indentation of a mapping entry (2:28)

1 | allowed-tools: Read, Bash, Grep, Glob
2 | argument-hint: [file-path] | [commit-hash] | --full
--------------------------------^
3 | description: Comprehensive code quality review with securit ...

components/commands/utilities/code-to-task.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/context-prime.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/debug-error.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/directory-deep-dive.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/explain-code.md

  • Errors: 2

  • Warnings: 0

  • Score: 90/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)
      semantic: 1 error(s)
    • SEM_E005: Credential harvesting pattern detected

components/commands/utilities/fix-issue.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/generate-linear-worklog.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/git-status.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/initref.md

  • Errors: 1

  • Warnings: 1

  • Score: 94/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/prime.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/refactor-code.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E001: Missing YAML frontmatter (must start with --- and end with ---)

components/commands/utilities/ultra-think.md

  • Errors: 1

  • Warnings: 0

  • Score: 95/100

    structural: 1 error(s)

    • STRUCT_E006: Missing required field: name

📊 View full report in workflow artifacts

@davila7 davila7 merged commit 4b5c071 into main Jan 8, 2026
4 of 5 checks passed
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

2 issues found across 4 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="cli-tool/components/skills/document-processing/json-canvas/SKILL.md">

<violation number="1" location="cli-tool/components/skills/document-processing/json-canvas/SKILL.md:596">
P2: Invalid hexadecimal example in ID documentation. The example `a3b2c1d0e9f8g7h6` contains 'g' and 'h' which are not valid hex characters (hex uses only 0-9 and a-f). This could mislead users into generating invalid IDs.</violation>
</file>

<file name="docs/components.json">

<violation number="1" location="docs/components.json:10730">
P2: Invalid hexadecimal example in ID generation documentation. The example `a3b2c1d0e9f8g7h6` contains 'g' and 'h' which are not valid hex digits (hex uses 0-9 and a-f only). This contradicts the stated format of "16-character lowercase hex string" and could cause the model to generate invalid IDs when following this skill.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.


```json
"id": "6f0ad84f44ce9c17"
"id": "a3b2c1d0e9f8g7h6"
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Jan 8, 2026

Choose a reason for hiding this comment

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

P2: Invalid hexadecimal example in ID documentation. The example a3b2c1d0e9f8g7h6 contains 'g' and 'h' which are not valid hex characters (hex uses only 0-9 and a-f). This could mislead users into generating invalid IDs.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/skills/document-processing/json-canvas/SKILL.md, line 596:

<comment>Invalid hexadecimal example in ID documentation. The example `a3b2c1d0e9f8g7h6` contains 'g' and 'h' which are not valid hex characters (hex uses only 0-9 and a-f). This could mislead users into generating invalid IDs.</comment>

<file context>
@@ -0,0 +1,643 @@
+
+```json
+"id": "6f0ad84f44ce9c17"
+"id": "a3b2c1d0e9f8g7h6"
+"id": "1234567890abcdef"
+```
</file context>
Suggested change
"id": "a3b2c1d0e9f8g7h6"
"id": "a3b2c1d0e9f87a6b"
Fix with Cubic

@@ -10722,6 +10722,57 @@
"lastValidated": null
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Jan 8, 2026

Choose a reason for hiding this comment

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

P2: Invalid hexadecimal example in ID generation documentation. The example a3b2c1d0e9f8g7h6 contains 'g' and 'h' which are not valid hex digits (hex uses 0-9 and a-f only). This contradicts the stated format of "16-character lowercase hex string" and could cause the model to generate invalid IDs when following this skill.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/components.json, line 10730:

<comment>Invalid hexadecimal example in ID generation documentation. The example `a3b2c1d0e9f8g7h6` contains 'g' and 'h' which are not valid hex digits (hex uses 0-9 and a-f only). This contradicts the stated format of "16-character lowercase hex string" and could cause the model to generate invalid IDs when following this skill.</comment>

<file context>
@@ -10722,6 +10722,57 @@
+      "path": "document-processing/json-canvas",
+      "category": "document-processing",
+      "type": "skill",
+      "content": "---\nname: json-canvas\ndescription: Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.\n---\n\n# JSON Canvas Skill\n\nThis skill enables Claude Code to create and edit valid JSON Canvas files (`.canvas`) used in Obsidian and other applications.\n\n## Overview\n\nJSON Canvas is an open file format for infinite canvas data. Canvas files use the `.canvas` extension and contain valid JSON following the [JSON Canvas Spec 1.0](https://jsoncanvas.org/spec/1.0/).\n\n## File Structure\n\nA canvas file contains two top-level arrays:\n\n```json\n{\n  \"nodes\": [],\n  \"edges\": []\n}\n```\n\n- `nodes` (optional): Array of node objects\n- `edges` (optional): Array of edge objects connecting nodes\n\n## Nodes\n\nNodes are objects placed on the canvas. There are four node types:\n- `text` - Text content with Markdown\n- `file` - Reference to files/attachments\n- `link` - External URL\n- `group` - Visual container for other nodes\n\n### Z-Index Ordering\n\nNodes are ordered by z-index in the array:\n- First node = bottom layer (displayed below others)\n- Last node = top layer (displayed above others)\n\n### Generic Node Attributes\n\nAll nodes share these attributes:\n\n| Attribute | Required | Type | Description |\n|-----------|----------|------|-------------|\n| `id` | Yes | string | Unique identifier for the node |\n| `type` | Yes | string | Node type: `text`, `file`, `link`, or `group` |\n| `x` | Yes | integer | X position in pixels |\n| `y` | Yes | integer | Y position in pixels |\n| `width` | Yes | integer | Width in pixels |\n| `height` | Yes | integer | Height in pixels |\n| `color` | No | canvasColor | Node color (see Color section) |\n\n### Text Nodes\n\nText nodes contain Markdown content.\n\n```json\n{\n  \"id\": \"6f0ad84f44ce9c17\",\n  \"type\": \"text\",\n  \"x\": 0,\n  \"y\": 0,\n  \"width\": 400,\n  \"height\": 200,\n  \"text\": \"# Hello World\\n\\nThis is **Markdown** content.\"\n}\n```\n\n| Attribute | Required | Type | Description |\n|-----------|----------|------|-------------|\n| `text` | Yes | string | Plain text with Markdown syntax |\n\n### File Nodes\n\nFile nodes reference files or attachments (images, videos, PDFs, notes, etc.).\n\n```json\n{\n  \"id\": \"a1b2c3d4e5f67890\",\n  \"type\": \"file\",\n  \"x\": 500,\n  \"y\": 0,\n  \"width\": 400,\n  \"height\": 300,\n  \"file\": \"Attachments/diagram.png\"\n}\n```\n\n```json\n{\n  \"id\": \"b2c3d4e5f6789012\",\n  \"type\": \"file\",\n  \"x\": 500,\n  \"y\": 400,\n  \"width\": 400,\n  \"height\": 300,\n  \"file\": \"Notes/Project Overview.md\",\n  \"subpath\": \"#Implementation\"\n}\n```\n\n| Attribute | Required | Type | Description |\n|-----------|----------|------|-------------|\n| `file` | Yes | string | Path to file within the system |\n| `subpath` | No | string | Link to heading or block (starts with `#`) |\n\n### Link Nodes\n\nLink nodes display external URLs.\n\n```json\n{\n  \"id\": \"c3d4e5f678901234\",\n  \"type\": \"link\",\n  \"x\": 1000,\n  \"y\": 0,\n  \"width\": 400,\n  \"height\": 200,\n  \"url\": \"https://obsidian.md\"\n}\n```\n\n| Attribute | Required | Type | Description |\n|-----------|----------|------|-------------|\n| `url` | Yes | string | External URL |\n\n### Group Nodes\n\nGroup nodes are visual containers for organizing other nodes.\n\n```json\n{\n  \"id\": \"d4e5f6789012345a\",\n  \"type\": \"group\",\n  \"x\": -50,\n  \"y\": -50,\n  \"width\": 1000,\n  \"height\": 600,\n  \"label\": \"Project Overview\",\n  \"color\": \"4\"\n}\n```\n\n```json\n{\n  \"id\": \"e5f67890123456ab\",\n  \"type\": \"group\",\n  \"x\": 0,\n  \"y\": 700,\n  \"width\": 800,\n  \"height\": 500,\n  \"label\": \"Resources\",\n  \"background\": \"Attachments/background.png\",\n  \"backgroundStyle\": \"cover\"\n}\n```\n\n| Attribute | Required | Type | Description |\n|-----------|----------|------|-------------|\n| `label` | No | string | Text label for the group |\n| `background` | No | string | Path to background image |\n| `backgroundStyle` | No | string | Background rendering style |\n\n#### Background Styles\n\n| Value | Description |\n|-------|-------------|\n| `cover` | Fills entire width and height of node |\n| `ratio` | Maintains aspect ratio of background image |\n| `repeat` | Repeats image as pattern in both directions |\n\n## Edges\n\nEdges are lines connecting nodes.\n\n```json\n{\n  \"id\": \"f67890123456789a\",\n  \"fromNode\": \"6f0ad84f44ce9c17\",\n  \"toNode\": \"a1b2c3d4e5f67890\"\n}\n```\n\n```json\n{\n  \"id\": \"0123456789abcdef\",\n  \"fromNode\": \"6f0ad84f44ce9c17\",\n  \"fromSide\": \"right\",\n  \"fromEnd\": \"none\",\n  \"toNode\": \"b2c3d4e5f6789012\",\n  \"toSide\": \"left\",\n  \"toEnd\": \"arrow\",\n  \"color\": \"1\",\n  \"label\": \"leads to\"\n}\n```\n\n| Attribute | Required | Type | Default | Description |\n|-----------|----------|------|---------|-------------|\n| `id` | Yes | string | - | Unique identifier for the edge |\n| `fromNode` | Yes | string | - | Node ID where connection starts |\n| `fromSide` | No | string | - | Side where edge starts |\n| `fromEnd` | No | string | `none` | Shape at edge start |\n| `toNode` | Yes | string | - | Node ID where connection ends |\n| `toSide` | No | string | - | Side where edge ends |\n| `toEnd` | No | string | `arrow` | Shape at edge end |\n| `color` | No | canvasColor | - | Line color |\n| `label` | No | string | - | Text label for the edge |\n\n### Side Values\n\n| Value | Description |\n|-------|-------------|\n| `top` | Top edge of node |\n| `right` | Right edge of node |\n| `bottom` | Bottom edge of node |\n| `left` | Left edge of node |\n\n### End Shapes\n\n| Value | Description |\n|-------|-------------|\n| `none` | No endpoint shape |\n| `arrow` | Arrow endpoint |\n\n## Colors\n\nThe `canvasColor` type can be specified in two ways:\n\n### Hex Colors\n\n```json\n{\n  \"color\": \"#FF0000\"\n}\n```\n\n### Preset Colors\n\n```json\n{\n  \"color\": \"1\"\n}\n```\n\n| Preset | Color |\n|--------|-------|\n| `\"1\"` | Red |\n| `\"2\"` | Orange |\n| `\"3\"` | Yellow |\n| `\"4\"` | Green |\n| `\"5\"` | Cyan |\n| `\"6\"` | Purple |\n\nNote: Specific color values for presets are intentionally undefined, allowing applications to use their own brand colors.\n\n## Complete Examples\n\n### Simple Canvas with Text and Connections\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"8a9b0c1d2e3f4a5b\",\n      \"type\": \"text\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 300,\n      \"height\": 150,\n      \"text\": \"# Main Idea\\n\\nThis is the central concept.\"\n    },\n    {\n      \"id\": \"1a2b3c4d5e6f7a8b\",\n      \"type\": \"text\",\n      \"x\": 400,\n      \"y\": -100,\n      \"width\": 250,\n      \"height\": 100,\n      \"text\": \"## Supporting Point A\\n\\nDetails here.\"\n    },\n    {\n      \"id\": \"2b3c4d5e6f7a8b9c\",\n      \"type\": \"text\",\n      \"x\": 400,\n      \"y\": 100,\n      \"width\": 250,\n      \"height\": 100,\n      \"text\": \"## Supporting Point B\\n\\nMore details.\"\n    }\n  ],\n  \"edges\": [\n    {\n      \"id\": \"3c4d5e6f7a8b9c0d\",\n      \"fromNode\": \"8a9b0c1d2e3f4a5b\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"1a2b3c4d5e6f7a8b\",\n      \"toSide\": \"left\"\n    },\n    {\n      \"id\": \"4d5e6f7a8b9c0d1e\",\n      \"fromNode\": \"8a9b0c1d2e3f4a5b\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"2b3c4d5e6f7a8b9c\",\n      \"toSide\": \"left\"\n    }\n  ]\n}\n```\n\n### Project Board with Groups\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"5e6f7a8b9c0d1e2f\",\n      \"type\": \"group\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 300,\n      \"height\": 500,\n      \"label\": \"To Do\",\n      \"color\": \"1\"\n    },\n    {\n      \"id\": \"6f7a8b9c0d1e2f3a\",\n      \"type\": \"group\",\n      \"x\": 350,\n      \"y\": 0,\n      \"width\": 300,\n      \"height\": 500,\n      \"label\": \"In Progress\",\n      \"color\": \"3\"\n    },\n    {\n      \"id\": \"7a8b9c0d1e2f3a4b\",\n      \"type\": \"group\",\n      \"x\": 700,\n      \"y\": 0,\n      \"width\": 300,\n      \"height\": 500,\n      \"label\": \"Done\",\n      \"color\": \"4\"\n    },\n    {\n      \"id\": \"8b9c0d1e2f3a4b5c\",\n      \"type\": \"text\",\n      \"x\": 20,\n      \"y\": 50,\n      \"width\": 260,\n      \"height\": 80,\n      \"text\": \"## Task 1\\n\\nImplement feature X\"\n    },\n    {\n      \"id\": \"9c0d1e2f3a4b5c6d\",\n      \"type\": \"text\",\n      \"x\": 370,\n      \"y\": 50,\n      \"width\": 260,\n      \"height\": 80,\n      \"text\": \"## Task 2\\n\\nReview PR #123\",\n      \"color\": \"2\"\n    },\n    {\n      \"id\": \"0d1e2f3a4b5c6d7e\",\n      \"type\": \"text\",\n      \"x\": 720,\n      \"y\": 50,\n      \"width\": 260,\n      \"height\": 80,\n      \"text\": \"## Task 3\\n\\n~~Setup CI/CD~~\"\n    }\n  ],\n  \"edges\": []\n}\n```\n\n### Research Canvas with Files and Links\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"1e2f3a4b5c6d7e8f\",\n      \"type\": \"text\",\n      \"x\": 300,\n      \"y\": 200,\n      \"width\": 400,\n      \"height\": 200,\n      \"text\": \"# Research Topic\\n\\n## Key Questions\\n\\n- How does X affect Y?\\n- What are the implications?\",\n      \"color\": \"5\"\n    },\n    {\n      \"id\": \"2f3a4b5c6d7e8f9a\",\n      \"type\": \"file\",\n      \"x\": 0,\n      \"y\": 0,\n      \"width\": 250,\n      \"height\": 150,\n      \"file\": \"Literature/Paper A.pdf\"\n    },\n    {\n      \"id\": \"3a4b5c6d7e8f9a0b\",\n      \"type\": \"file\",\n      \"x\": 0,\n      \"y\": 200,\n      \"width\": 250,\n      \"height\": 150,\n      \"file\": \"Notes/Meeting Notes.md\",\n      \"subpath\": \"#Key Insights\"\n    },\n    {\n      \"id\": \"4b5c6d7e8f9a0b1c\",\n      \"type\": \"link\",\n      \"x\": 0,\n      \"y\": 400,\n      \"width\": 250,\n      \"height\": 100,\n      \"url\": \"https://example.com/research\"\n    },\n    {\n      \"id\": \"5c6d7e8f9a0b1c2d\",\n      \"type\": \"file\",\n      \"x\": 750,\n      \"y\": 150,\n      \"width\": 300,\n      \"height\": 250,\n      \"file\": \"Attachments/diagram.png\"\n    }\n  ],\n  \"edges\": [\n    {\n      \"id\": \"6d7e8f9a0b1c2d3e\",\n      \"fromNode\": \"2f3a4b5c6d7e8f9a\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"1e2f3a4b5c6d7e8f\",\n      \"toSide\": \"left\",\n      \"label\": \"supports\"\n    },\n    {\n      \"id\": \"7e8f9a0b1c2d3e4f\",\n      \"fromNode\": \"3a4b5c6d7e8f9a0b\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"1e2f3a4b5c6d7e8f\",\n      \"toSide\": \"left\",\n      \"label\": \"informs\"\n    },\n    {\n      \"id\": \"8f9a0b1c2d3e4f5a\",\n      \"fromNode\": \"4b5c6d7e8f9a0b1c\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"1e2f3a4b5c6d7e8f\",\n      \"toSide\": \"left\",\n      \"toEnd\": \"arrow\",\n      \"color\": \"6\"\n    },\n    {\n      \"id\": \"9a0b1c2d3e4f5a6b\",\n      \"fromNode\": \"1e2f3a4b5c6d7e8f\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"5c6d7e8f9a0b1c2d\",\n      \"toSide\": \"left\",\n      \"label\": \"visualized by\"\n    }\n  ]\n}\n```\n\n### Flowchart\n\n```json\n{\n  \"nodes\": [\n    {\n      \"id\": \"a0b1c2d3e4f5a6b7\",\n      \"type\": \"text\",\n      \"x\": 200,\n      \"y\": 0,\n      \"width\": 150,\n      \"height\": 60,\n      \"text\": \"**Start**\",\n      \"color\": \"4\"\n    },\n    {\n      \"id\": \"b1c2d3e4f5a6b7c8\",\n      \"type\": \"text\",\n      \"x\": 200,\n      \"y\": 100,\n      \"width\": 150,\n      \"height\": 60,\n      \"text\": \"Step 1:\\nGather data\"\n    },\n    {\n      \"id\": \"c2d3e4f5a6b7c8d9\",\n      \"type\": \"text\",\n      \"x\": 200,\n      \"y\": 200,\n      \"width\": 150,\n      \"height\": 80,\n      \"text\": \"**Decision**\\n\\nIs data valid?\",\n      \"color\": \"3\"\n    },\n    {\n      \"id\": \"d3e4f5a6b7c8d9e0\",\n      \"type\": \"text\",\n      \"x\": 400,\n      \"y\": 200,\n      \"width\": 150,\n      \"height\": 60,\n      \"text\": \"Process data\"\n    },\n    {\n      \"id\": \"e4f5a6b7c8d9e0f1\",\n      \"type\": \"text\",\n      \"x\": 0,\n      \"y\": 200,\n      \"width\": 150,\n      \"height\": 60,\n      \"text\": \"Request new data\",\n      \"color\": \"1\"\n    },\n    {\n      \"id\": \"f5a6b7c8d9e0f1a2\",\n      \"type\": \"text\",\n      \"x\": 400,\n      \"y\": 320,\n      \"width\": 150,\n      \"height\": 60,\n      \"text\": \"**End**\",\n      \"color\": \"4\"\n    }\n  ],\n  \"edges\": [\n    {\n      \"id\": \"a6b7c8d9e0f1a2b3\",\n      \"fromNode\": \"a0b1c2d3e4f5a6b7\",\n      \"fromSide\": \"bottom\",\n      \"toNode\": \"b1c2d3e4f5a6b7c8\",\n      \"toSide\": \"top\"\n    },\n    {\n      \"id\": \"b7c8d9e0f1a2b3c4\",\n      \"fromNode\": \"b1c2d3e4f5a6b7c8\",\n      \"fromSide\": \"bottom\",\n      \"toNode\": \"c2d3e4f5a6b7c8d9\",\n      \"toSide\": \"top\"\n    },\n    {\n      \"id\": \"c8d9e0f1a2b3c4d5\",\n      \"fromNode\": \"c2d3e4f5a6b7c8d9\",\n      \"fromSide\": \"right\",\n      \"toNode\": \"d3e4f5a6b7c8d9e0\",\n      \"toSide\": \"left\",\n      \"label\": \"Yes\",\n      \"color\": \"4\"\n    },\n    {\n      \"id\": \"d9e0f1a2b3c4d5e6\",\n      \"fromNode\": \"c2d3e4f5a6b7c8d9\",\n      \"fromSide\": \"left\",\n      \"toNode\": \"e4f5a6b7c8d9e0f1\",\n      \"toSide\": \"right\",\n      \"label\": \"No\",\n      \"color\": \"1\"\n    },\n    {\n      \"id\": \"e0f1a2b3c4d5e6f7\",\n      \"fromNode\": \"e4f5a6b7c8d9e0f1\",\n      \"fromSide\": \"top\",\n      \"fromEnd\": \"none\",\n      \"toNode\": \"b1c2d3e4f5a6b7c8\",\n      \"toSide\": \"left\",\n      \"toEnd\": \"arrow\"\n    },\n    {\n      \"id\": \"f1a2b3c4d5e6f7a8\",\n      \"fromNode\": \"d3e4f5a6b7c8d9e0\",\n      \"fromSide\": \"bottom\",\n      \"toNode\": \"f5a6b7c8d9e0f1a2\",\n      \"toSide\": \"top\"\n    }\n  ]\n}\n```\n\n## ID Generation\n\nNode and edge IDs must be unique strings. Obsidian generates 16-character hexadecimal IDs:\n\n```json\n\"id\": \"6f0ad84f44ce9c17\"\n\"id\": \"a3b2c1d0e9f8g7h6\"\n\"id\": \"1234567890abcdef\"\n```\n\nThis format is a 16-character lowercase hex string (64-bit random value).\n\n## Layout Guidelines\n\n### Positioning\n\n- Coordinates can be negative (canvas extends infinitely)\n- `x` increases to the right\n- `y` increases downward\n- Position refers to top-left corner of node\n\n### Recommended Sizes\n\n| Node Type | Suggested Width | Suggested Height |\n|-----------|-----------------|------------------|\n| Small text | 200-300 | 80-150 |\n| Medium text | 300-450 | 150-300 |\n| Large text | 400-600 | 300-500 |\n| File preview | 300-500 | 200-400 |\n| Link preview | 250-400 | 100-200 |\n| Group | Varies | Varies |\n\n### Spacing\n\n- Leave 20-50px padding inside groups\n- Space nodes 50-100px apart for readability\n- Align nodes to grid (multiples of 10 or 20) for cleaner layouts\n\n## Validation Rules\n\n1. All `id` values must be unique across nodes and edges\n2. `fromNode` and `toNode` must reference existing node IDs\n3. Required fields must be present for each node type\n4. `type` must be one of: `text`, `file`, `link`, `group`\n5. `backgroundStyle` must be one of: `cover`, `ratio`, `repeat`\n6. `fromSide`, `toSide` must be one of: `top`, `right`, `bottom`, `left`\n7. `fromEnd`, `toEnd` must be one of: `none`, `arrow`\n8. Color presets must be `\"1\"` through `\"6\"` or valid hex color\n\n## References\n\n- [JSON Canvas Spec 1.0](https://jsoncanvas.org/spec/1.0/)\n- [JSON Canvas GitHub](https://github.com/obsidianmd/jsoncanvas)\n\n",
+      "description": "Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.",
+      "downloads": 0,
</file context>
Fix with Cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants