Skip to content

fix(agents): remove hardcoded developer path from hooks-guide bash steps#1050

Open
xiaolai wants to merge 1 commit into
alirezarezvani:mainfrom
xiaolai:fix/nlpm-hardcoded-path-hooks-guide
Open

fix(agents): remove hardcoded developer path from hooks-guide bash steps#1050
xiaolai wants to merge 1 commit into
alirezarezvani:mainfrom
xiaolai:fix/nlpm-hardcoded-path-hooks-guide

Conversation

@xiaolai

@xiaolai xiaolai commented Apr 30, 2026

Copy link
Copy Markdown

Automated: drive-by fix from NLPM, an NL artifact linter. Reviewed and reproduced before submission.

Bug: Steps 2 (both variants) in hooks-guide.md hardcode /Users/rezarezvani/projects/claude-code-skills-factory — this path does not exist on any other machine, so the hook generation steps fail with a directory-not-found error for all users.

Evidence: grep -n 'rezarezvani' .claude/agents/hooks-guide.md returns lines 253 and 259; running cd /Users/rezarezvani/projects/claude-code-skills-factory on a clean checkout exits with No such file or directory.

Fix: Remove the cd /absolute/path && prefix from both bash blocks, leaving only the python3 generated-skills/hook-factory/hook_factory.py ... invocation — consistent with Step 3 (validator.py) which already uses a relative path.

Steps 5–6 in the hook generation workflow were hardcoded to
/Users/rezarezvani/projects/claude-code-skills-factory, causing a
directory-not-found error on every non-developer machine. The subsequent
validator step (Step 3) already uses a relative path — this commit
makes Steps 5–6 consistent with that pattern.

Co-Authored-By: Claude Code <noreply@anthropic.com>
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