codeforge-dev 1.13.0 → 1.14.2

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/scripts/skill-suggester.py

@@ -2,7 +2,7 @@
 """Skill suggester hook for UserPromptSubmit and SubagentStart events.
 
 Detects which hook event called it via input JSON shape:
-- UserPromptSubmit: {"prompt": "..."} -> {"systemMessage": "..."}
+- UserPromptSubmit: {"prompt": "..."} -> {"additionalContext": "..."}
 - SubagentStart:    {"subagent_type": "Plan", "prompt": "..."} -> {"additionalContext": "..."}
 
 Matches user prompts against skill keyword maps (phrases + terms) and suggests
@@ -16,30 +16,33 @@ import sys
 SKILLS = {
     "fastapi": {
         "phrases": [
-            "rest api",
+            "build a fastapi app",
+            "rest api with fastapi",
             "fastapi",
             "fast api",
+            "add sse streaming",
+            "dependency injection in fastapi",
+            "define pydantic models",
+            "stream llm responses",
+            "add middleware to fastapi",
             "pydantic model",
-            "sse streaming",
-            "server-sent event",
-            "dependency injection",
-            "asgi middleware",
-            "api endpoint",
-            "api route",
         ],
-        "terms": ["fastapi", "pydantic", "uvicorn", "starlette"],
+        "terms": ["fastapi", "pydantic", "uvicorn", "starlette", "sse-starlette"],
     },
     "sqlite": {
         "phrases": [
             "sqlite",
+            "set up a sqlite database",
             "wal mode",
             "fts5",
             "full-text search",
             "better-sqlite3",
             "cloudflare d1",
-            "json1 extension",
+            "store json in sqlite",
+            "write ctes",
+            "window functions",
         ],
-        "terms": ["aiosqlite"],
+        "terms": ["aiosqlite", "better-sqlite3"],
     },
     "claude-code-headless": {
         "phrases": [
@@ -49,31 +52,39 @@ SKILLS = {
             "claude code headless",
             "run claude in ci",
             "claude in pipeline",
+            "parse stream-json output",
+            "track costs programmatically",
+            "permissions for scripts",
         ],
-        "terms": [],
+        "terms": ["--output-format stream-json", "--permission-mode"],
     },
     "claude-agent-sdk": {
         "phrases": [
             "agent sdk",
             "claude agent sdk",
-            "build an agent",
-            "create an agent",
+            "build an agent with the claude agent sdk",
             "canusetool",
             "sdk permissions",
+            "create mcp tools",
+            "define subagents",
+            "configure sdk hooks",
+            "stream sdk messages",
         ],
-        "terms": ["claude-agent-sdk", "claude_agent_sdk"],
+        "terms": ["claude-agent-sdk", "claude_agent_sdk", "createSdkMcpServer"],
     },
     "pydantic-ai": {
         "phrases": [
             "pydantic ai",
             "pydantic-ai",
             "pydanticai",
-            "ai agent",
-            "runcontext",
-            "vercel ai adapter",
-            "model fallback",
+            "build a pydanticai agent",
+            "add tools to an agent",
+            "stream responses with pydanticai",
+            "test a pydanticai agent",
+            "connect pydanticai to svelte",
+            "configure model fallbacks",
         ],
-        "terms": ["pydanticai"],
+        "terms": ["pydanticai", "RunContext", "VercelAIAdapter", "FallbackModel"],
     },
     "testing": {
         "phrases": [
@@ -87,12 +98,11 @@ SKILLS = {
             "mock dependencies",
             "test endpoint",
             "test component",
+            "test sse streaming",
             "unit test",
             "integration test",
-            "run tests",
-            "run the tests",
         ],
-        "terms": ["pytest", "vitest"],
+        "terms": ["pytest", "vitest", "pytest-anyio", "httpx AsyncClient"],
     },
     "docker-py": {
         "phrases": [
@@ -102,8 +112,12 @@ SKILLS = {
             "docker engine api",
             "docker from python",
             "docker api",
+            "manage docker containers from python",
+            "create containers programmatically",
+            "stream container logs",
+            "monitor container health from python",
         ],
-        "terms": ["aiodocker"],
+        "terms": ["aiodocker", "DockerClient"],
     },
     "svelte5": {
         "phrases": [
@@ -113,12 +127,11 @@ SKILLS = {
             "svelte rune",
             "svelte 5",
             "svelte5",
-            "layercake",
-            "layer cake",
-            "svelte-dnd-action",
-            "svelte dnd",
+            "migrate from svelte 4",
+            "manage state with $state",
+            "drag and drop to svelte",
         ],
-        "terms": ["sveltekit", "svelte"],
+        "terms": ["sveltekit", "svelte", "svelte-dnd-action", "@ai-sdk/svelte"],
     },
     "docker": {
         "phrases": [
@@ -129,11 +142,10 @@ SKILLS = {
             "multi-stage build",
             "health check",
             "healthcheck",
-            "docker network",
-            "docker volume",
-            "docker image",
+            "docker compose watch",
+            "optimize docker image",
         ],
-        "terms": ["dockerfile", "compose"],
+        "terms": ["dockerfile", "compose.yaml", "BuildKit"],
     },
     "skill-building": {
         "phrases": [
@@ -144,6 +156,8 @@ SKILLS = {
             "skill instructions",
             "skill authoring",
             "design a skill",
+            "improve a skill description",
+            "optimize skill content",
         ],
         "terms": [],
     },
@@ -151,49 +165,46 @@ SKILLS = {
         "phrases": [
             "debug logs",
             "check logs",
+            "check container logs",
             "find error",
             "investigate failure",
-            "container logs",
             "what went wrong",
             "why did this crash",
             "diagnose the issue",
             "look at the logs",
             "read the logs",
+            "read docker logs",
             "analyze error",
         ],
-        "terms": ["diagnose", "troubleshoot"],
+        "terms": ["diagnose", "troubleshoot", "OOMKilled", "ECONNREFUSED"],
     },
     "refactoring-patterns": {
         "phrases": [
             "refactor this",
             "clean up code",
-            "improve code structure",
-            "reduce complexity",
-        ],
-        "terms": [
-            "refactor",
-            "refactoring",
-            "code smell",
-            "extract function",
-            "dead code",
+            "clean up this function",
+            "extract a method",
+            "fix code smells",
+            "reduce code duplication",
+            "simplify this class",
+            "break up this large function",
+            "remove dead code",
         ],
+        "terms": ["refactor", "refactoring", "code smell", "feature envy", "god class"],
     },
     "security-checklist": {
         "phrases": [
             "security review",
+            "security issues",
+            "security vulnerabilities",
             "check for vulnerabilities",
+            "scan for secrets",
             "audit security",
-            "find security issues",
-        ],
-        "terms": [
-            "security",
-            "vulnerability",
-            "owasp",
-            "injection",
-            "xss",
-            "secrets",
-            "cve",
+            "review for injection",
+            "owasp compliance",
+            "hardcoded credentials",
         ],
+        "terms": ["owasp", "injection", "xss", "cve", "trivy", "gitleaks"],
     },
     "git-forensics": {
         "phrases": [
@@ -201,62 +212,67 @@ SKILLS = {
             "who changed this",
             "when did this break",
             "git blame",
+            "bisect a regression",
+            "recover a lost commit",
+            "search git history",
+            "find when code was removed",
+            "trace the history",
+            "use git reflog",
         ],
-        "terms": ["bisect", "blame", "archaeology", "git log", "pickaxe", "reflog"],
+        "terms": ["bisect", "blame", "pickaxe", "reflog", "git log -S"],
     },
     "specification-writing": {
         "phrases": [
             "write a spec",
+            "write requirements",
             "define requirements",
             "acceptance criteria",
             "user stories",
+            "use ears format",
+            "given/when/then",
+            "write given/when/then scenarios",
+            "structure requirements",
         ],
-        "terms": [
-            "specification",
-            "requirements",
-            "ears",
-            "gherkin",
-            "given when then",
-        ],
+        "terms": ["specification", "ears", "gherkin", "given when then"],
     },
     "performance-profiling": {
         "phrases": [
+            "profile this code",
             "profile performance",
             "find bottleneck",
+            "find the bottleneck",
             "benchmark this",
+            "create a flamegraph",
+            "find memory leaks",
             "why is this slow",
+            "measure execution time",
+            "reduce latency",
         ],
-        "terms": [
-            "profiling",
-            "benchmark",
-            "flamegraph",
-            "bottleneck",
-            "latency",
-            "throughput",
-        ],
+        "terms": ["cProfile", "py-spy", "scalene", "flamegraph", "hyperfine"],
     },
     "api-design": {
         "phrases": [
             "api design",
             "rest api design",
             "design an api",
-            "design a rest",
-            "api convention",
-            "endpoint design",
+            "design rest endpoints",
             "api versioning",
-            "pagination pattern",
-            "error response format",
+            "pagination strategy",
+            "design error responses",
+            "rate limiting",
+            "openapi documentation",
         ],
-        "terms": ["openapi", "swagger", "rfc7807"],
+        "terms": ["openapi", "swagger", "rfc7807", "rfc 7807"],
     },
     "ast-grep-patterns": {
         "phrases": [
             "ast-grep",
             "ast grep",
             "structural search",
-            "structural code search",
             "syntax-aware search",
-            "tree-sitter",
+            "find code patterns",
+            "search with ast-grep",
+            "use tree-sitter",
         ],
         "terms": ["sg run", "ast-grep", "tree-sitter"],
     },
@@ -269,6 +285,7 @@ SKILLS = {
             "license check",
             "unused dependencies",
             "vulnerability scan",
+            "find unused dependencies",
         ],
         "terms": ["pip-audit", "npm audit", "cargo audit", "govulncheck"],
     },
@@ -279,10 +296,10 @@ SKILLS = {
             "add docstrings",
             "add jsdoc",
             "document the api",
-            "documentation template",
+            "create architecture docs",
             "update the docs",
         ],
-        "terms": ["docstring", "jsdoc", "tsdoc", "godoc", "rustdoc"],
+        "terms": ["docstring", "jsdoc", "tsdoc", "rustdoc", "Sphinx"],
     },
     "migration-patterns": {
         "phrases": [
@@ -293,8 +310,10 @@ SKILLS = {
             "bump python",
             "upgrade pydantic",
             "migrate express",
+            "modernize the codebase",
+            "commonjs to esm",
         ],
-        "terms": ["migrate", "migration", "upgrade"],
+        "terms": ["migrate", "migration"],
     },
     "spec-build": {
         "phrases": [
@@ -302,10 +321,9 @@ SKILLS = {
             "build from spec",
             "start building",
             "spec-build",
-            "implement this feature from the spec",
+            "implement this feature",
             "build what the spec describes",
-            "implement from the spec",
-            "build the feature",
+            "run spec-build",
         ],
         "terms": ["spec-build"],
     },
@@ -317,9 +335,86 @@ SKILLS = {
             "spec-review",
             "does code match spec",
             "audit implementation",
+            "run spec-review",
+            "regression check",
         ],
         "terms": ["spec-review"],
     },
+    "spec-check": {
+        "phrases": [
+            "check spec health",
+            "audit specs",
+            "which specs are stale",
+            "find missing specs",
+            "review spec quality",
+            "run spec-check",
+            "are my specs up to date",
+        ],
+        "terms": ["spec-check"],
+    },
+    "spec-init": {
+        "phrases": [
+            "initialize specs",
+            "specs directory",
+            "set up specs",
+            "bootstrap specs",
+            "start using specs",
+            "create spec directory",
+            "init specs",
+            "set up .specs",
+        ],
+        "terms": ["spec-init"],
+    },
+    "spec-new": {
+        "phrases": [
+            "create a spec",
+            "new spec",
+            "new feature spec",
+            "write a spec for",
+            "spec this feature",
+            "start a new spec",
+            "plan a feature",
+            "add a spec",
+        ],
+        "terms": ["spec-new"],
+    },
+    "spec-refine": {
+        "phrases": [
+            "refine the spec",
+            "review spec assumptions",
+            "validate spec decisions",
+            "approve the spec",
+            "walk me through the spec",
+            "check spec for assumptions",
+            "iterate on the spec",
+        ],
+        "terms": ["spec-refine"],
+    },
+    "spec-update": {
+        "phrases": [
+            "update the spec",
+            "mark spec as implemented",
+            "as-built update",
+            "finish the spec",
+            "close the spec",
+            "update spec status",
+            "sync spec with code",
+        ],
+        "terms": ["spec-update"],
+    },
+    "team": {
+        "phrases": [
+            "spawn a team",
+            "create a team",
+            "team of agents",
+            "use a swarm",
+            "work in parallel",
+            "coordinate multiple agents",
+            "split this across agents",
+            "team up",
+        ],
+        "terms": ["TeamCreate", "SendMessage"],
+    },
 }
 
 # Pre-compile term patterns for whole-word matching
@@ -370,25 +465,19 @@ def main() -> None:
         return
 
     skill_list = ", ".join(f'"{s}"' for s in skills)
-    is_subagent = "subagent_type" in data
 
-    if is_subagent:
-        output = {
+    output = {
+        "hookSpecificOutput": {
+            "hookEventName": "UserPromptSubmit",
             "additionalContext": (
-                f"Available skills matching this planning task: {skill_list}. "
-                "These skills contain project-specific patterns, conventions, "
-                "and reference material. Consider their guidance when designing "
-                "the implementation approach."
-            )
-        }
-    else:
-        output = {
-            "systemMessage": (
-                f"<system-reminder>The user's prompt matches available skill(s): "
-                f"{skill_list}. Load the relevant skill(s) using the Skill tool "
-                f"before responding.</system-reminder>"
-            )
+                f"MANDATORY — Skill activation required. The user's prompt matches: {skill_list}. "
+                f"Before responding, evaluate each matched skill: is it relevant to this specific request? "
+                f"For each relevant skill, activate it using the Skill tool NOW. "
+                f"Skip any that are not relevant to the user's actual intent. "
+                f"Do not proceed with implementation until relevant skills are loaded."
+            ),
         }
+    }
 
     json.dump(output, sys.stdout)
 

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/api-design/SKILL.md

@@ -1,12 +1,15 @@
 ---
 name: api-design
 description: >-
-  This skill should be used when the user asks to "design an API",
-  "design REST endpoints", "plan API versioning", "choose pagination strategy",
-  "design error responses", "API conventions", "endpoint design",
-  "create API documentation", or discusses REST API design, HTTP method
-  semantics, status code selection, authentication patterns, or rate limiting.
-version: 0.1.0
+  Provides REST API design guidance covering resource naming, pagination
+  strategies, error responses, versioning, and authentication patterns. USE
+  WHEN the user asks to "design an API", "design REST endpoints", "plan API
+  versioning", "choose a pagination strategy", "design error responses",
+  "set up rate limiting", "create OpenAPI documentation", or works with REST
+  conventions, HTTP method semantics, cursor pagination, RFC 7807, JWT auth,
+  status codes. DO NOT USE for API implementation code — use the fastapi skill
+  for building endpoints.
+version: 0.2.0
 ---
 
 # API Design

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/ast-grep-patterns/SKILL.md

@@ -1,12 +1,13 @@
 ---
 name: ast-grep-patterns
 description: >-
-  This skill should be used when the user asks to "use ast-grep",
-  "structural search", "syntax-aware search", "find code patterns",
-  "search with ast-grep", "use tree-sitter", "find function calls structurally",
-  or discusses ast-grep patterns, structural code search, meta-variables,
-  tree-sitter parsing, or syntax-aware code matching.
-version: 0.1.0
+  Teaches syntax-aware code search using ast-grep (sg) and tree-sitter with
+  meta-variable patterns for functions, imports, and classes. USE WHEN the
+  user asks to "use ast-grep", "structural search", "find code patterns",
+  "search with ast-grep", "use tree-sitter", "syntax-aware search", or works
+  with sg run, $$$ARGS meta-variables, tree-sitter tags. DO NOT USE for
+  simple text searches where Grep suffices.
+version: 0.2.0
 ---
 
 # AST-Grep Patterns

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/claude-agent-sdk/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: claude-agent-sdk
 description: >-
-  This skill should be used when the user asks to "build an agent with the Claude Agent SDK",
-  "use the Claude Agent SDK", "create an agent with TypeScript SDK", "configure SDK permissions",
-  "use canUseTool callback", "create custom MCP tools with createSdkMcpServer",
-  "manage SDK sessions", "define subagents", "configure SDK hooks",
-  "set up SDK sandbox", "stream SDK messages", "use sdk query function",
-  or discusses Claude Agent SDK TypeScript integration, SDK permission modes,
-  SDK message types, agent definitions, or programmatic Claude agent orchestration.
-version: 0.1.0
+  Provides Claude Agent SDK patterns in TypeScript covering query function,
+  permissions, MCP tools, subagents, and hooks. USE WHEN the user asks to
+  "build an agent with the Claude Agent SDK", "use canUseTool callback",
+  "create MCP tools with createSdkMcpServer", "define subagents", "configure
+  SDK hooks", "stream SDK messages", or works with @anthropic-ai/claude-agent-sdk,
+  query(), PermissionResult, AgentDefinition. DO NOT USE for PydanticAI Python
+  agents or Claude Code CLI headless mode.
+version: 0.2.0
 ---
 
 # Claude Agent SDK (TypeScript)

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/claude-code-headless/SKILL.md

@@ -1,15 +1,14 @@
 ---
 name: claude-code-headless
 description: >-
-  This skill should be used when the user asks to "run Claude Code in headless mode",
-  "use claude -p for automation", "parse stream-json output from Claude Code",
-  "use the Claude Agent SDK", "run Claude Code in CI/CD",
-  "configure MCP servers for headless Claude",
-  "set up Claude Code permissions for scripts",
-  "track Claude Code costs programmatically", or discusses Claude Code
-  print mode, non-interactive pipelines, SDK integration in TypeScript or Python,
-  structured output with json-schema, or session management for automation.
-version: 0.1.0
+  Guides non-interactive Claude Code usage via the -p flag, stream-json output
+  parsing, and CI/CD pipeline integration. USE WHEN the user asks to "run
+  Claude Code in headless mode", "use claude -p for automation", "parse
+  stream-json output", "run Claude Code in CI/CD", "track costs
+  programmatically", "set up permissions for scripts", or works with
+  --output-format stream-json, --permission-mode, --json-schema, --resume.
+  DO NOT USE for the TypeScript SDK API — use claude-agent-sdk instead.
+version: 0.2.0
 ---
 
 # Claude Code Headless

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/debugging/SKILL.md

@@ -1,13 +1,17 @@
 ---
 name: debugging
 description: >-
-  This skill should be used when the user asks to "debug logs", "check logs",
-  "find error in logs", "read docker logs", "investigate failure",
-  "check container logs", "analyze error output", "find what went wrong",
-  "why did this crash", "check what happened", "diagnose the issue",
-  "look at the logs", or discusses log analysis, container debugging,
-  error investigation, crash diagnosis, or service failure troubleshooting.
-version: 0.1.0
+  Guides systematic log analysis and error diagnosis across Docker, systemd,
+  and application environments using forensic investigation methodology.
+  USE WHEN the user asks to "debug logs", "check container logs",
+  "why did this crash", "investigate failure", "find error in logs",
+  "read docker logs", "diagnose the issue", or "analyze error output",
+  or works with Docker exit codes, Python tracebacks, ECONNREFUSED,
+  OOMKilled, or journalctl. DO NOT USE for performance profiling,
+  security auditing, or dependency vulnerability scanning.
+version: 0.2.0
+allowed-tools: Bash, Read, Glob, Grep
+argument-hint: "[service or log-path]"
 ---
 
 # Debugging & Log Analysis

package/.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/dependency-management/SKILL.md

@@ -1,12 +1,16 @@
 ---
 name: dependency-management
 description: >-
-  This skill should be used when the user asks to "check dependencies",
-  "audit dependencies", "find outdated packages", "check dependency health",
-  "scan for vulnerabilities", "find unused dependencies", "license check",
-  "npm audit", "pip audit", "cargo audit", or discusses dependency analysis,
-  supply chain security, package version gaps, or license compliance.
-version: 0.1.0
+  Provides a five-phase dependency health analysis covering outdated packages,
+  security vulnerabilities, unused deps, version conflicts, and license
+  compliance across npm, pip, cargo, and Go modules. USE WHEN the user asks
+  to "audit dependencies", "find outdated packages", "find unused
+  dependencies", "check dependency health", "license check", "npm audit",
+  "pip-audit", or "cargo audit", or works with supply chain security, CVSS
+  scores, or SPDX identifiers. DO NOT USE for general security code review
+  or application-level vulnerability scanning.
+version: 0.2.0
+allowed-tools: Bash, Read, Glob, Grep
 ---
 
 # Dependency Management