Verify you're in the correct project location before implementing features to avoid duplicate work and context switching.
Overview
Starting work in the wrong project directory or worktree can lead to wasted effort, duplicate implementations, and unnecessary context switching. This skill helps you establish the correct location early.
Steps
Confirm Current Location
Check the current working directory and active file paths
Verify the project name matches your intended target
Look for key identifying files (package.json, .git, README.md, etc.)
Cross-Reference Project Details
If working with multiple worktrees or branches, explicitly confirm which one is active
Review recent commits or branch information to ensure you're on the right track
Ask for clarification if the project location is ambiguous
Proceed Only When Certain
Don't begin implementation until you've confirmed the location
If uncertain, ask the user to explicitly confirm the project path
Switch locations if needed before starting work
Tips
Always verify location at the start of a new coding session
Pay special attention when working with multiple worktrees, branches, or similar project structures
Explicitly state the confirmed location in your response so the user can catch any mistakes early
This small upfront check prevents re-doing work in the wrong place
1---2name: verify-project-location3description: verify-project-location4---5# verify-project-location67Verify you're in the correct project location before implementing features to avoid duplicate work and context switching.89## Overview10Starting work in the wrong project directory or worktree can lead to wasted effort, duplicate implementations, and unnecessary context switching. This skill helps you establish the correct location early.1112## Steps13141. **Confirm Current Location**15 - Check the current working directory and active file paths16 - Verify the project name matches your intended target17 - Look for key identifying files (package.json, .git, README.md, etc.)18192. **Cross-Reference Project Details**20 - If working with multiple worktrees or branches, explicitly confirm which one is active21 - Review recent commits or branch information to ensure you're on the right track22 - Ask for clarification if the project location is ambiguous23243. **Proceed Only When Certain**25 - Don't begin implementation until you've confirmed the location26 - If uncertain, ask the user to explicitly confirm the project path27 - Switch locations if needed before starting work2829## Tips30- Always verify location at the start of a new coding session31- Pay special attention when working with multiple worktrees, branches, or similar project structures32- Explicitly state the confirmed location in your response so the user can catch any mistakes early33- This small upfront check prevents re-doing work in the wrong place
Run npx skillmds@latest add claudiawong522/verify-project-location in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
verify-project-location It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
claudiawong522 (@claudiawong522) published this skill. Their other Agent Skills are listed on their SkillMD profile.