How does the shell integration work for 'cd' commands?

Worktrunk writes shell commands to a temporary file specified by the WORKTRUNK_DIRECTIVE_FILE environment variable, which the shell wrapper then sources after the process exits.

How are parenthesized messages handled differently?

Supplementary stats are styled in gray (dim), whereas 'reason' parentheses that explain why an action is happening use the same color as the main message.

What is the standard for using symbols in messages?

Symbols like integration indicators (_) or diff markers (+/-) are treated as atomic units with specific colors (dim, green, or red) and should retain their native styling even inside colored messages.

When should I use stdout versus stderr?

Use stdout for machine-readable data intended for pipes or scripts (like JSON or tables). Use stderr for all human-facing content, including progress messages, errors, and hints.

Worktrunk CLI Output Standards

Name: Worktrunk CLI Output Standards
Author: max-sixty

bymax-sixty

•

1,610

Developer Tools

Enforces standardized CLI output formatting and shell integration patterns for the Worktrunk Git worktree manager.

About

The writing-user-outputs skill provides a comprehensive framework for creating consistent and user-friendly CLI interfaces within the Worktrunk ecosystem. It establishes clear protocols for shell integration via directive files, distinguishes between stdout for pipeable data and stderr for human-facing status, and defines a robust visual language using color-coded messages (success, progress, warnings, and errors). By following these standards, developers can ensure that parallel AI agent workflows provide clear, actionable feedback while maintaining compatibility across different terminal environments and Windows MSYS2/Git Bash systems.

Key Features

Cross-platform path handling for Git Bash and MSYS2 compatibility
Logical separation of data (stdout) and human status updates (stderr)
Automated shell integration for post-execution commands like directory switching
Refined messaging principles including flag acknowledgment and parallel structure
1,610 GitHub stars
Standardized color-coded message types for success, progress, hints, and errors

Use Cases

Developing shell-aware tools that need to trigger directory changes after exit
Standardizing output for new CLI commands to ensure UI consistency
Implementing background task reporting for complex Git worktree operations

About

Key Features

Cross-platform path handling for Git Bash and MSYS2 compatibility
Logical separation of data (stdout) and human status updates (stderr)
Automated shell integration for post-execution commands like directory switching
Refined messaging principles including flag acknowledgment and parallel structure
1,610 GitHub stars
Standardized color-coded message types for success, progress, hints, and errors

Use Cases

Developing shell-aware tools that need to trigger directory changes after exit
Standardizing output for new CLI commands to ensure UI consistency
Implementing background task reporting for complex Git worktree operations