git-worktree-status

To check background build and test status in a git worktree, use a status check skill that reads log files from the .worktree-logs directory, parses pass/fail counts, and reports a color-coded summary with actionable next steps.

Parsing background task results from .worktree-logs involves reading the stored log files to extract pass/fail counts and errors, then generating a color-coded summary to provide non-blocking feedback on type checks, tests, and builds.

Yes, you can get non-blocking status updates for git worktree verification tasks by running a status check command that parses background logs from the .worktree-logs directory to keep developers productive without waiting for builds.

No, git worktree status checking requires you to be inside a git worktree directory, as the skill must first detect the current worktree and then read the specific .worktree-logs directory within it to determine results.

The best way to monitor git worktree health is to run a dedicated status check command that parses .worktree-logs for background task results, providing a color-coded summary and actionable guidance for type checks, tests, and builds.

If your git worktree background task logs are not showing pass/fail results, verify that you are inside the correct git worktree and that the background verification tasks are correctly writing output to the .worktree-logs directory.