[stasadev]

Short Summary (TL;DR)

The review skill's env file is now review.env, sourced by its absolute path. An agent that ran source env in the review directory ran /usr/bin/env instead, so the next ddev command used the user's real global config.

The Issue

Bash's source looks a name without a slash up on PATH before the current directory. The review skill wrote its env file as env, so source env found /usr/bin/env and failed. Commands after it ran without DDEV_XDG_CONFIG_HOME. In one review, this started a test project in the user's own global config and recreated their ddev-router. Agents hit it in several reviews.

How This PR Solves The Issue

• The file is now review.env, which isn't on PATH.
• The example shows sourcing it by its absolute path in each later command.

Manual Testing Instructions

cd "$(mktemp -d "$HOME/tmp/env-test.XXXXXX")"
echo 'export X=ok' > env && echo 'export X=ok' > review.env
source env; echo "X=$X"
# Expect "source: /usr/bin/env: cannot execute binary file" and an empty X
source review.env; echo "X=$X"
# Expect X=ok

Automated Testing Overview

No tests cover skill text. Claude Code ran claude plugin validate ..

🤖 Generated with Claude Code