Harness Feature Lifecycle Manager FAQs

Question 1

Does this skill mock my backend services during testing?

Accepted Answer

No. Unlike traditional unit testing skills, Harness boots your actual development stack and runs tests against live services. This ensures that the code works in a real-world environment before it ever reaches the PR stage.

Question 2

Is it safe to use with my environment variables?

Accepted Answer

Yes. Harness is designed to copy existing .env files from your project root into the isolated worktree without ever printing, displaying, or logging the contents of those sensitive files.

Question 3

What tools are required for the 'pr' command to work?

Accepted Answer

The PR functionality requires the GitHub CLI (gh) to be installed and authenticated on your system, as it uses the CLI to push branches and generate pull request metadata.

Question 4

How does Harness prevent port conflicts between different features?

Accepted Answer

Harness uses a registry-based slot allocation strategy. Each new feature worktree is assigned a unique slot number, and service ports are automatically offset from their base values (e.g., 3000 becomes 3010, 3020, etc.) to ensure multiple environments can run concurrently.

Question 5

What happens if I don't have a harness.json file?

Accepted Answer

Harness includes an auto-detection fallback. It scans for common project markers like package.json or pyproject.toml to determine the appropriate install and start commands. If it can't identify the stack, it will ask the user for the necessary commands.

Harness Feature Lifecycle Manager

Harness Feature Lifecycle Manager

主要功能

使用场景

主要功能

使用场景