Fix 11 CodeRabbit review issues: docs consistency, MD040, missing content

- Move system prompt changelog entry from Added to Changed section
- Add Worktrees section to CLAUDE.md matching system prompt guidance
- Add language tags to 5 fenced code blocks (MD040) across SKILL.md
  and manual-worktree-commands.md
- Soften absolute merge conflict claim in parallel-workflow-patterns.md
- Add EnterWorktree to SKILL.md allowed-tools
- Add worktree to README.md skills list (21→22 entries)
- Fix stale skill counts: 21→22 in features/index.md,
  getting-started/index.md, plugins/skill-engine.md (description +
  table); 34→35 in reference/architecture.md

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -10,11 +10,11 @@
 #### Skills
 - **worktree** — New skill for git worktree creation, management, and cleanup. Covers `EnterWorktree` tool, `--worktree` CLI flag, `.worktreeinclude` setup, worktree naming conventions, cleanup lifecycle, and CodeForge integration (Project Manager auto-detection, agent isolation). Includes two reference files: manual worktree commands and parallel workflow patterns.
 
+### Changed
+
 #### System Prompt
 - **`<git_worktrees>` section** — Updated to document Claude Code native worktree convention (`<repo>/.claude/worktrees/`) as the recommended approach alongside the legacy `.worktrees/` convention. Added `EnterWorktree` tool guidance, `.worktreeinclude` file documentation, and path convention comparison table.
 
-### Changed
-
 #### Configuration
 - Moved `.claude` directory from `/workspaces/.claude` to `~/.claude` (home directory)
 - Added Docker named volume for persistence across rebuilds (per-instance isolation via `${devcontainerId}`)

.devcontainer/CLAUDE.md

@@ -33,6 +33,34 @@ CodeForge devcontainer for AI-assisted development with Claude Code.
 
 Config files deploy via `file-manifest.json` on every container start. Most deploy to `~/.claude/`; ccstatusline config deploys to `~/.config/ccstatusline/`. Each entry supports `overwrite`: `"if-changed"` (default, sha256), `"always"`, or `"never"`. Supported variables: `${CLAUDE_CONFIG_DIR}`, `${WORKSPACE_ROOT}`, `${HOME}`.
 
+## Worktrees
+
+Git worktrees allow checking out multiple branches simultaneously, each in its own directory.
+
+**Native (recommended for Claude Code sessions):**
+- **In-session:** `EnterWorktree` tool — creates worktree at `<repo>/.claude/worktrees/<name>/`, branch `worktree-<name>`, auto-cleaned if no changes
+- **New session:** `claude --worktree <name>` — starts Claude in its own worktree; combine with `--tmux` for background work
+
+**Manual (legacy convention):**
+```bash
+mkdir -p /workspaces/projects/.worktrees
+git worktree add /workspaces/projects/.worktrees/<branch-name> -b <branch>
+```
+
+**Environment files:** Place a `.worktreeinclude` file at the project root listing `.gitignore`-excluded files to copy into new worktrees (e.g., `.env`). Uses `.gitignore` pattern syntax; only files matching both `.worktreeinclude` and `.gitignore` are copied.
+
+**Management:**
+
+| Command | Purpose |
+|---------|---------|
+| `git worktree list` | Show all active worktrees |
+| `git worktree remove <path>` | Remove a worktree (destructive — confirm first) |
+| `git worktree prune` | Clean up stale references (destructive — confirm first) |
+
+**Path conventions:**
+- **Native:** `<repo>/.claude/worktrees/<name>/` — used by `--worktree` flag and `EnterWorktree`
+- **Legacy:** `.worktrees/` as sibling to the main repo — used for manual `git worktree add` and Project Manager integration
+
 ## Commands
 
 | Command | Purpose |

.devcontainer/README.md

@@ -348,7 +348,7 @@ Agent definitions in `plugins/devs-marketplace/plugins/agent-system/agents/` pro
 
 Skills in `plugins/devs-marketplace/plugins/skill-engine/skills/` provide domain-specific coding references:
 
-`api-design` · `ast-grep-patterns` · `claude-agent-sdk` · `claude-code-headless` · `debugging` · `dependency-management` · `docker` · `docker-py` · `documentation-patterns` · `fastapi` · `git-forensics` · `migration-patterns` · `performance-profiling` · `pydantic-ai` · `refactoring-patterns` · `security-checklist` · `skill-building` · `sqlite` · `svelte5` · `team` · `testing`
+`api-design` · `ast-grep-patterns` · `claude-agent-sdk` · `claude-code-headless` · `debugging` · `dependency-management` · `docker` · `docker-py` · `documentation-patterns` · `fastapi` · `git-forensics` · `migration-patterns` · `performance-profiling` · `pydantic-ai` · `refactoring-patterns` · `security-checklist` · `skill-building` · `sqlite` · `svelte5` · `team` · `testing` · `worktree`
 
 ### Spec Skills (8) — `spec-workflow` plugin
 

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

@@ -10,7 +10,7 @@ description: >-
   or parallel development patterns. DO NOT USE for routine git branching
   or single-branch workflows.
 version: 0.1.0
-allowed-tools: Bash, Read, Grep, Glob
+allowed-tools: Bash, Read, Grep, Glob, EnterWorktree
 ---
 
 # Git Worktrees
@@ -36,7 +36,7 @@ Use worktrees when:
 
 The fastest way to create a worktree during a Claude Code session. Call `EnterWorktree` with a descriptive name:
 
-```
+```text
 EnterWorktree: feature-auth-oauth2
 ```
 
@@ -129,7 +129,7 @@ git worktree list
 
 Output shows each worktree's path, HEAD commit, and branch:
 
-```
+```text
 /workspaces/projects/CodeForge            d2ba55e [main]
 /workspaces/projects/.worktrees/feature-a abc1234 [feature-a]
 ```

.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md

@@ -72,14 +72,14 @@ git worktree list --porcelain
 ```
 
 **Default output:**
-```
+```text
 /workspaces/projects/CodeForge            d2ba55e [main]
 /workspaces/projects/.worktrees/feature-a abc1234 [feature-a]
 /workspaces/projects/.worktrees/bugfix-b  def5678 [bugfix-b] locked
 ```
 
 **Porcelain output:**
-```
+```text
 worktree /workspaces/projects/CodeForge
 HEAD d2ba55eabc1234def5678901234567890abcdef
 branch refs/heads/main
@@ -168,7 +168,7 @@ git worktree unlock <path>
 
 The main repository has a `.git` **directory**. Each worktree has a `.git` **file** (not directory) containing a pointer:
 
-```
+```text
 gitdir: /workspaces/projects/CodeForge/.git/worktrees/feature-a
 ```
 

.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md

@@ -71,7 +71,7 @@ Agents with `isolation: worktree` in their frontmatter (refactorer, test-writer,
 **Workflow:**
 1. Each agent/session works on independent files
 2. Changes stay isolated until explicitly merged
-3. No merge conflicts during parallel work
+3. Reduced conflict risk when file ownership is respected
 4. After each session completes, review changes via PR
 
 **When to use:** Large tasks that decompose into independent workstreams. Effective for feature builds, migrations, or test suites where each agent owns a different set of files.

docs/src/content/docs/getting-started/index.md

@@ -42,7 +42,7 @@ If you already have Docker and VS Code installed, you can go from zero to a runn
 Plugins are the backbone of CodeForge. They hook into Claude Code's lifecycle to enhance, guard, and automate your workflow. Highlights include:
 
 - **Agent System** — 17 specialized agents for architecture, debugging, testing, security, and more
-- **Skill Engine** — 21 domain-specific knowledge packs covering frameworks, patterns, and workflows
+- **Skill Engine** — 22 domain-specific knowledge packs covering frameworks, patterns, and workflows
 - **Spec Workflow** — specification-driven development with 8 lifecycle skills
 - **Session Context** — automatic git state injection, TODO harvesting, and commit reminders
 - **Auto Code Quality** — formatting, linting, and advisory test runs on every change

docs/src/content/docs/plugins/skill-engine.md

@@ -1,6 +1,6 @@
 ---
 title: Skill Engine
-description: The skill engine plugin provides 21 domain-specific knowledge packs with automatic suggestion based on conversation context.
+description: The skill engine plugin provides 22 domain-specific knowledge packs with automatic suggestion based on conversation context.
 sidebar:
   order: 3
 ---
@@ -78,6 +78,7 @@ Skills for working with Claude Code itself and extending CodeForge.
 | **git-forensics** | Git history analysis, blame, bisect, pickaxe search, reflog recovery |
 | **ast-grep-patterns** | AST-grep pattern writing for syntax-aware code search |
 | **team** | Multi-agent team coordination, task decomposition, parallel workstreams |
+| **worktree** | Git worktree lifecycle, EnterWorktree tool, `.worktreeinclude` setup, parallel workflows |
 
 :::note[Cross-Plugin Skills]
 The `specification-writing` skill and the spec lifecycle skills (`spec-new`, `spec-build`, etc.) live in the [Spec Workflow](./spec-workflow/) plugin, not the skill engine. However, the skill-suggester registers keywords for them so they are auto-suggested alongside skill-engine skills.

docs/src/content/docs/reference/architecture.md

@@ -111,7 +111,7 @@ Skills are Markdown knowledge files loaded on demand during a session:
 4. The skill content is injected into the conversation context
 5. Claude uses the skill knowledge for the current task
 
-CodeForge ships 34 skills across the skill-engine, spec-workflow, ticket-workflow, and agent-system plugins.
+CodeForge ships 35 skills across the skill-engine, spec-workflow, ticket-workflow, and agent-system plugins.
 
 ## Directory Structure