Fix symlink path in Windows installation instructions

[itsjinendrajain]

Summary

Updated the installation docs to fix Windows (PowerShell) setup and correct the symlink/junction path so users can successfully link the skills directory.

Motivation and Context

The previous Windows instructions had an incorrect path (~\.codex inside $env:USERPROFILE) and included a broken/duplicate command. This caused junction creation to fail, so Codex/agents could not load the skills.

How Has This Been Tested?

Tested on Windows PowerShell by:

• Creating "$env:USERPROFILE\.agents\skills"
• Running the corrected mklink /J command
• Verifying the junction points to "$env:USERPROFILE\.codex\superpowers\skills" and that the folder opens correctly.

Breaking Changes

No.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the [MCP Documentation](https://modelcontextprotocol.io)
• My code follows the repository's style guidelines
• New and existing tests pass locally (docs-only change)
• I have added appropriate error handling (N/A for docs, but commands are corrected)
• I have added or updated documentation as needed

Additional context

Windows junctions (mklink /J) do not understand ~ like PowerShell does, so the path must be explicit. The updated command uses "$env:USERPROFILE\.codex\..." which works reliably.

[coderabbitai]

📝 Walkthrough

Walkthrough

The installation documentation for Windows is updated to reference the home directory using a tilde-expanded path (~/.codex) instead of direct environment variable expansion when creating the symlink junction point.

Changes

Cohort / File(s)	Summary
Windows Installation Path Update .codex/INSTALL.md	Modified the target path in the Windows symlink command from $env:USERPROFILE\.codex\superpowers\skills to $env:USERPROFILE\~\.codex\superpowers\skills to use tilde-expanded home directory notation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Fix ~/ path expansion on Windows — use $HOME instead #428: Updates the same installation command paths in .codex/INSTALL.md for Windows home-directory path expansion using tilde notation.
• Migrate Codex integration from bootstrap CLI to native skill discovery #430: Modifies the Windows symlink junction command and target paths for the same Codex to ~/.agents/skills symlink configuration.
• fix codex path in release notes #155: Updates incorrect Codex path references in documentation by changing paths to use hidden .codex/ or tilde-expanded ~/.codex notation.

Poem

🐰 A tilde hops through Windows paths so grand,
Where home directories now stand,
The symlink dances with expanded grace,
Finding skills in their rightful place! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: fixing a symlink path in Windows installation instructions, which matches the core objective of the PR.
Description check	✅ Passed	The description provides comprehensive context about the Windows installation bug, the root cause, testing approach, and reasoning for the fix, directly related to 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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.codex/INSTALL.md:
- Line 25: The mklink command in the diff uses an incorrect target path
containing a literal "\~\" segment; update the mklink /J invocation (the command
string containing "$env:USERPROFILE\.agents\skills\superpowers" and
"$env:USERPROFILE\~\.codex\superpowers\skills") to remove the spurious "\~\" so
the target is "$env:USERPROFILE\.codex\superpowers\skills", ensuring the
junction points to %USERPROFILE%\.codex\superpowers\skills.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e4a2375 and a9bd42f.

📒 Files selected for processing (1)

• .codex/INSTALL.md

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Spurious \~\ in the target path produces a wrong directory — this fix is broken.

The updated target path "$env:USERPROFILE\~\.codex\superpowers\skills" does not resolve to %USERPROFILE%\.codex\superpowers\skills. Because ~ is not a special character inside a Windows path, this expands literally to C:\Users\<user>\~\.codex\superpowers\skills — a subdirectory named ~ that almost certainly does not exist, causing the junction creation to fail (or point to the wrong location).

The mklink /J syntax is mklink /J <link> <target>, so the argument order is fine, but the target path must be corrected by removing the extra \~\ segment:

🐛 Proposed fix

-  cmd /c mklink /J "$env:USERPROFILE\.agents\skills\superpowers" "$env:USERPROFILE\~\.codex\superpowers\skills"
+  cmd /c mklink /J "$env:USERPROFILE\.agents\skills\superpowers" "$env:USERPROFILE\.codex\superpowers\skills"

📝 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

	cmd /c mklink /J "$env:USERPROFILE\.agents\skills\superpowers" "$env:USERPROFILE\~\.codex\superpowers\skills"
	cmd /c mklink /J "$env:USERPROFILE\.agents\skills\superpowers" "$env:USERPROFILE\.codex\superpowers\skills"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.codex/INSTALL.md at line 25, The mklink command in the diff uses an
incorrect target path containing a literal "\~\" segment; update the mklink /J
invocation (the command string containing
"$env:USERPROFILE\.agents\skills\superpowers" and
"$env:USERPROFILE\~\.codex\superpowers\skills") to remove the spurious "\~\" so
the target is "$env:USERPROFILE\.codex\superpowers\skills", ensuring the
junction points to %USERPROFILE%\.codex\superpowers\skills.

[obra]

Thanks for looking at the Windows install path, but this change introduces a bug: $env:USERPROFILE already resolves to the full home directory (e.g. C:\Users\user), so adding ~\ makes the path C:\Users\user\~\.codex\... — a literal tilde directory that doesn't exist. The current path on dev ($env:USERPROFILE\.codex\superpowers\skills) is correct.