Skip to content

Add worktree skill for git worktree lifecycle#5

Merged
AnExiledDev merged 2 commits intomainfrom
feature/worktree-skill
Feb 26, 2026
Merged

Add worktree skill for git worktree lifecycle#5
AnExiledDev merged 2 commits intomainfrom
feature/worktree-skill

Conversation

@AnExiledDev
Copy link
Owner

@AnExiledDev AnExiledDev commented Feb 24, 2026

Summary

  • New worktree skill in the skill-engine plugin — full-lifecycle guide covering EnterWorktree tool (primary), --worktree CLI flag, manual git worktree commands, .worktreeinclude setup, worktree management, and CodeForge integration (Project Manager auto-detection, agent isolation)
  • Two reference files: manual worktree command reference and parallel workflow patterns (feature+review, safe experimentation, agent swarm, hotfix, long-running migration)
  • System prompt update: <git_worktrees> section now documents Claude Code native convention (<repo>/.claude/worktrees/) as recommended alongside legacy .worktrees/ path, adds EnterWorktree guidance and .worktreeinclude documentation
  • Auto-suggestion: skill-suggester.py updated with worktree keyword entry (10 phrases, 3 terms)
  • Skill count 21→22 across all READMEs, docs pages, plugin.json, Hero component, and CLAUDE.md

Test plan

  • Load skill via /worktree in a Claude session — verify SKILL.md activates
  • Test auto-suggestion with prompts like "create a worktree" or "enter worktree"
  • Verify EnterWorktree creates worktree at native path
  • Confirm setup-projects.sh detects worktrees in .worktrees/
  • Review docs site skill count renders as 22

Summary by CodeRabbit

  • New Features

    • Added a "worktree" skill to CodeForge for Git worktree workflows; skill count increased from 21 to 22.
    • New in-session and new-session worktree flows with automated creation, naming, and safe cleanup.
  • Documentation

    • Expanded guidance on worktree workflows, environment handling, path conventions, management commands, lifecycle, patterns, and safety best practices.
    • Added comprehensive reference and usage guides for worktree operations.

@coderabbitai
Copy link

coderabbitai bot commented Feb 24, 2026

Warning

Rate limit exceeded

@AnExiledDev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 7 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4c2eec4 and 5f4c787.

📒 Files selected for processing (19)
  • .devcontainer/CHANGELOG.md
  • .devcontainer/CLAUDE.md
  • .devcontainer/README.md
  • .devcontainer/config/defaults/main-system-prompt.md
  • .devcontainer/docs/plugins.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/.claude-plugin/plugin.json
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/README.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/scripts/skill-suggester.py
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md
  • README.md
  • docs/src/components/Hero.astro
  • docs/src/content/docs/features/skills.md
  • docs/src/content/docs/getting-started/first-session.md
  • docs/src/content/docs/getting-started/index.md
  • docs/src/content/docs/plugins/index.md
  • docs/src/content/docs/plugins/skill-engine.md
  • docs/src/content/docs/reference/architecture.md
📝 Walkthrough

Walkthrough

The changes add a new "worktree" skill to the CodeForge skill-engine (increasing skills from 21 to 22), introduce comprehensive worktree documentation and references, update skill counts across docs and site components, and add skill-suggester detection for worktree-related prompts. System prompt guidance for worktrees is also expanded.

Changes

Cohort / File(s) Summary
Changelog and Main Documentation
\.devcontainer/CHANGELOG.md, README.md, \.devcontainer/README.md, \.devcontainer/CLAUDE.md
Added Unreleased changelog entry and updated skill counts/CLAUDE plugin listing to reflect the new worktree skill (21 → 22).
System Prompt Configuration
\.devcontainer/config/defaults/main-system-prompt.md
Replaced legacy git-worktree layout guidance with Claude Code–centric workflows: EnterWorktree tool, --worktree CLI usage, .worktreeinclude env files, path conventions (native vs legacy), management commands, and safety notes.
Skill-Engine Plugin Manifest & README
\.devcontainer/docs/plugins.md, \.devcontainer/plugins/devs-marketplace/plugins/skill-engine/.claude-plugin/plugin.json, \.devcontainer/plugins/devs-marketplace/plugins/skill-engine/README.md
Bumped skill-engine description and docs from 21 → 22 skills; added worktree entry to plugin README and catalog.
Skill Suggester Logic
\.devcontainer/plugins/devs-marketplace/plugins/skill-engine/scripts/skill-suggester.py
Added new "worktree" key to SKILLS with phrases and terms for detection (e.g., "create a worktree", "git worktree", "EnterWorktree").
Worktree Skill Docs
\.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
New comprehensive skill guide covering mental model, creation flows (EnterWorktree, CLI --worktree, manual git worktree add), .worktreeinclude behavior, initialization steps, management, CodeForge integration, and path conventions.
Worktree Reference Materials
\.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md, \.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md
Two new reference docs: one for Git worktree subcommands, examples, troubleshooting; another describing parallel workflow patterns, anti-patterns, and lifecycle hooks.
Web Documentation Updates
docs/src/components/Hero.astro, docs/src/content/docs/features/index.md, docs/src/content/docs/features/skills.md, docs/src/content/docs/getting-started/first-session.md, docs/src/content/docs/getting-started/index.md, docs/src/content/docs/plugins/index.md, docs/src/content/docs/plugins/skill-engine.md, docs/src/content/docs/reference/architecture.md
Updated site content and components to reflect 22 skills (added worktree references, updated counts and skill listings across pages).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 Noses twitch, paws tap the ground,
Worktrees sprout without a sound.
Twenty-two skills hopping free,
Branches, clones, and harmony,
Into Claude's burrow we go — tidy and proud! 🌿

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add worktree skill for git worktree lifecycle' clearly and specifically summarizes the main change: adding a new worktree skill. It is concise, directly related to the primary objective, and accurately represents the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/worktree-skill

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 11

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.devcontainer/CHANGELOG.md:
- Around line 5-11: The changelog places the "`<git_worktrees>` section" note
under "### Added" but it documents an update to existing behavior; move that
bullet (the line mentioning `"<git_worktrees>" section` and its details about
the Claude Code native worktree convention, `EnterWorktree` guidance, and
`.worktreeinclude` file documentation) from the "### Added" block into a "###
Changed" block so it correctly reflects a change rather than a new addition.

In @.devcontainer/config/defaults/main-system-prompt.md:
- Around line 341-363: The CLAUDE.md doc is missing the new worktree guidance
present in main-system-prompt.md; add a "Worktrees" section to
.devcontainer/CLAUDE.md that copies the same guidance: describe native usage
(EnterWorktree tool and the --worktree <name> flag creating
<repo>/.claude/worktrees/<name>/ with branch worktree-<name> and auto-clean
behavior), the manual legacy approach (mkdir .worktrees + git worktree add
/workspaces/projects/.worktrees/<branch-name> -b <branch>), explain
.worktreeinclude behavior (files must match .worktreeinclude and .gitignore),
list management commands (git worktree list, git worktree remove <path>, git
worktree prune) and state the path conventions (native vs legacy .worktrees/);
ensure terminology matches exactly (EnterWorktree, --worktree, .worktreeinclude,
.worktrees) so readers can map config to docs.

In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md:
- Around line 75-90: Add language tags (e.g., ```text) to the three fenced code
blocks that are missing them: the block starting with
"/workspaces/projects/CodeForge            d2ba55e [main]" (first diff block),
the block starting with "worktree /workspaces/projects/CodeForge" (porcelain
output block), and the block containing "gitdir:
/workspaces/projects/CodeForge/.git/worktrees/feature-a"; update each opening
fence to include a language specifier like "text" so markdownlint MD040 is
satisfied.

In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md:
- Line 74: Replace the absolute statement "No merge conflicts during parallel
work" with a softened claim that reflects reality; update the phrase in the
document (the heading/text that currently reads "No merge conflicts during
parallel work") to something like "Reduces conflict risk when file ownership is
respected" or equivalent, so it no longer guarantees zero conflicts and aligns
with the caution on Line 79.

In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md:
- Around line 39-41: Two fenced code blocks in SKILL.md (the one containing
"EnterWorktree: feature-auth-oauth2" and the block showing the worktree listing)
lack language identifiers and trigger markdownlint MD040; update both fenced
blocks to include a language tag (e.g., change ``` to ```text) so the blocks
around the "EnterWorktree: feature-auth-oauth2" snippet and the worktree listing
(lines referenced in the review, including the other block at 132-135) are
fenced as ```text.
- Line 13: The allowed-tools list is missing EnterWorktree while the document
references EnterWorktree as the primary method; update the allowed-tools entry
(the YAML key named allowed-tools) to include EnterWorktree alongside Bash,
Read, Grep, Glob so the documented primary workflow (EnterWorktree references on
lines ~35–42, 65, 85, 142, 203, 212) is permitted and consistent with the
document.

In @.devcontainer/README.md:
- Line 332: Update the General Skills list for the skill-engine plugin to
include the missing "worktree" entry so the list matches the header "General
Skills (22) — `skill-engine`"; locate the README section titled "General Skills
(22) — `skill-engine`" and insert "worktree" into the enumerated skills list
(maintain the same formatting as the other entries) and verify the total count
reflects 22 items.

In `@docs/src/content/docs/features/index.md`:
- Line 46: The Feature Summary table is inconsistent: the body text uses "**22
domain-specific knowledge packs**" but the summary row still lists "21"; update
the summary row count from 21 to 22 so the page is consistent. Locate the
"Feature Summary" table row that currently shows "21" (the summary row) and
change that cell to "22" to match the paragraph that reads "**22 domain-specific
knowledge packs**". Ensure any other occurrences of "21" in the same document
referring to the skills count are updated to "22".

In `@docs/src/content/docs/getting-started/index.md`:
- Line 8: Update the inconsistent skill count in the Getting Started doc: locate
the sentence containing "Skill Engine has 21 knowledge packs" (the line that
still reads 21) and change the number to 22 so it matches the other occurrences
(lines that say 22); ensure any nearby mentions of knowledge packs/skills in the
same paragraph are adjusted consistently.

In `@docs/src/content/docs/plugins/skill-engine.md`:
- Line 38: Update the page so the displayed skill count and tables match: change
the header sentence "CodeForge ships with 21 skills" to 22 (the lines currently
stating 22 at 38 and 174 are correct but the top-of-page count at line 3 must be
updated), add the missing "worktree" entry to the skills tables where it's
absent, and ensure any other summary counts or lists on this page reflect the
new total of 22 skills (search for the phrase "CodeForge ships with" and the
skills table blocks and update them).

In `@docs/src/content/docs/reference/architecture.md`:
- Line 149: The table row for "skill-engine/" was updated to 22 but the summary
elsewhere still reads "34 skills"; update the stale aggregate string "34 skills"
to "35 skills" so the combined total matches (search for the literal "34 skills"
in the same document and replace it with "35 skills", e.g., near the summary
paragraph that references the total skills count).

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d2ba55e and b9f14e6.

📒 Files selected for processing (20)
  • .devcontainer/CHANGELOG.md
  • .devcontainer/CLAUDE.md
  • .devcontainer/README.md
  • .devcontainer/config/defaults/main-system-prompt.md
  • .devcontainer/docs/plugins.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/.claude-plugin/plugin.json
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/README.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/scripts/skill-suggester.py
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md
  • README.md
  • docs/src/components/Hero.astro
  • docs/src/content/docs/features/index.md
  • docs/src/content/docs/features/skills.md
  • docs/src/content/docs/getting-started/first-session.md
  • docs/src/content/docs/getting-started/index.md
  • docs/src/content/docs/plugins/index.md
  • docs/src/content/docs/plugins/skill-engine.md
  • docs/src/content/docs/reference/architecture.md

## Skills

**21 domain-specific knowledge packs** give Claude deep expertise in frameworks, patterns, and workflows. When you start discussing FastAPI routes or Svelte 5 runes, the skill engine detects the context and auto-suggests the relevant skill. Once loaded, the skill injects structured knowledge — best practices, code patterns, API references, and common pitfalls — directly into Claude's context for the current task.
**22 domain-specific knowledge packs** give Claude deep expertise in frameworks, patterns, and workflows. When you start discussing FastAPI routes or Svelte 5 runes, the skill engine detects the context and auto-suggests the relevant skill. Once loaded, the skill injects structured knowledge — best practices, code patterns, API references, and common pitfalls — directly into Claude's context for the current task.
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Feature Summary table still has the old skills count.

Lines 46/58 say 22 skills, but the summary row at Line 93 still lists 21. Please update that row to keep the page consistent.

Suggested doc patch
-| [Skills](./skills/) | 21 | FastAPI, Svelte 5, Docker, Testing, Debugging, Security, and 15 more |
+| [Skills](./skills/) | 22 | FastAPI, Svelte 5, Docker, Testing, Debugging, Security, and 16 more |

As per coding guidelines docs/**: User-facing documentation changes MUST be reflected in relevant pages in docs/ if the docs site exists.

Also applies to: 58-58

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/src/content/docs/features/index.md` at line 46, The Feature Summary
table is inconsistent: the body text uses "**22 domain-specific knowledge
packs**" but the summary row still lists "21"; update the summary row count from
21 to 22 so the page is consistent. Locate the "Feature Summary" table row that
currently shows "21" (the summary row) and change that cell to "22" to match the
paragraph that reads "**22 domain-specific knowledge packs**". Ensure any other
occurrences of "21" in the same document referring to the skills count are
updated to "22".

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md:
- Around line 104-107: The wording in the "Rules" section is ambiguous—reword
the `.worktreeinclude` rule so it clearly states that files listed in
`.worktreeinclude` will be copied only if they are untracked (i.e., ignored by
Git via `.gitignore`), and that tracked files are never duplicated; update the
sentence that currently reads "Only files matching both `.worktreeinclude` and
`.gitignore` are copied" to something like: "Only files listed in
`.worktreeinclude` that are untracked/ignored by Git (per `.gitignore`) are
copied; tracked files come from the checkout and are not duplicated." Ensure
this change is applied in the "Rules:" block of SKILL.md and references the
`.worktreeinclude` and `.gitignore` patterns.
- Around line 130-135: Update the example output for `git worktree list` in
SKILL.md to use the native-path-as-primary convention described earlier: replace
the legacy `.worktrees/feature-a` path with the native path format used by
EnterWorktree/--worktree (e.g., `<repo>/.claude/worktrees/<name>/feature-a`) and
keep the same HEAD/branch columns so the example matches the documented workflow
and symbols `EnterWorktree`, `--worktree`, and `git worktree list`.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b9f14e6 and 4c2eec4.

📒 Files selected for processing (10)
  • .devcontainer/CHANGELOG.md
  • .devcontainer/CLAUDE.md
  • .devcontainer/README.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md
  • docs/src/content/docs/features/index.md
  • docs/src/content/docs/getting-started/index.md
  • docs/src/content/docs/plugins/skill-engine.md
  • docs/src/content/docs/reference/architecture.md
✅ Files skipped from review due to trivial changes (2)
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/parallel-workflow-patterns.md
  • .devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/references/manual-worktree-commands.md
🚧 Files skipped from review as they are similar to previous changes (3)
  • .devcontainer/CHANGELOG.md
  • docs/src/content/docs/plugins/skill-engine.md
  • .devcontainer/README.md

Comment on lines +104 to +107
**Rules:**
- Uses `.gitignore` pattern syntax
- Only files matching **both** `.worktreeinclude` and `.gitignore` are copied
- Tracked files are never duplicated (they come from the checkout itself)
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Clarify the .worktreeinclude copy rule — "matching both" is ambiguous.

The phrase "Only files matching both .worktreeinclude and .gitignore are copied" reads as if a user must list the file in both .worktreeinclude and .gitignore to trigger copying. The actual intent is that only untracked (gitignored) files listed in .worktreeinclude are copied. Rephrasing avoids the misread:

✏️ Proposed clarification
-Only files matching **both** `.worktreeinclude` and `.gitignore` are copied
+Only untracked files (those already excluded by `.gitignore`) that are listed in `.worktreeinclude` are copied
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Rules:**
- Uses `.gitignore` pattern syntax
- Only files matching **both** `.worktreeinclude` and `.gitignore` are copied
- Tracked files are never duplicated (they come from the checkout itself)
**Rules:**
- Uses `.gitignore` pattern syntax
- Only untracked files (those already excluded by `.gitignore`) that are listed in `.worktreeinclude` are copied
- Tracked files are never duplicated (they come from the checkout itself)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
around lines 104 - 107, The wording in the "Rules" section is ambiguous—reword
the `.worktreeinclude` rule so it clearly states that files listed in
`.worktreeinclude` will be copied only if they are untracked (i.e., ignored by
Git via `.gitignore`), and that tracked files are never duplicated; update the
sentence that currently reads "Only files matching both `.worktreeinclude` and
`.gitignore` are copied" to something like: "Only files listed in
`.worktreeinclude` that are untracked/ignored by Git (per `.gitignore`) are
copied; tracked files come from the checkout and are not duplicated." Ensure
this change is applied in the "Rules:" block of SKILL.md and references the
`.worktreeinclude` and `.gitignore` patterns.

Comment on lines +130 to +135
Output shows each worktree's path, HEAD commit, and branch:

```text
/workspaces/projects/CodeForge d2ba55e [main]
/workspaces/projects/.worktrees/feature-a abc1234 [feature-a]
```
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

git worktree list example only shows the legacy path — inconsistent with the native-path-as-primary narrative.

The example output on lines 132-135 shows a .worktrees/feature-a (legacy convention) path. A user who followed the recommended EnterWorktree/--worktree workflow will see <repo>/.claude/worktrees/<name>/ in real output, not .worktrees/. This makes the example misleading immediately after the document establishes the native path as primary.

✏️ Proposed update
-/workspaces/projects/CodeForge            d2ba55e [main]
-/workspaces/projects/.worktrees/feature-a abc1234 [feature-a]
+/workspaces/projects/CodeForge                              d2ba55e [main]
+/workspaces/projects/CodeForge/.claude/worktrees/feature-a abc1234 [worktree-feature-a]
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Output shows each worktree's path, HEAD commit, and branch:
```text
/workspaces/projects/CodeForge d2ba55e [main]
/workspaces/projects/.worktrees/feature-a abc1234 [feature-a]
```
Output shows each worktree's path, HEAD commit, and branch:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
@.devcontainer/plugins/devs-marketplace/plugins/skill-engine/skills/worktree/SKILL.md
around lines 130 - 135, Update the example output for `git worktree list` in
SKILL.md to use the native-path-as-primary convention described earlier: replace
the legacy `.worktrees/feature-a` path with the native path format used by
EnterWorktree/--worktree (e.g., `<repo>/.claude/worktrees/<name>/feature-a`) and
keep the same HEAD/branch columns so the example matches the documented workflow
and symbols `EnterWorktree`, `--worktree`, and `git worktree list`.

New skill-engine skill covering EnterWorktree, --worktree CLI flag,
.worktreeinclude setup, worktree management, and CodeForge integration.
Updates system prompt <git_worktrees> to recommend native Claude Code
convention alongside legacy .worktrees/ path.
…tent

- 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
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.

1 participant