Pipeloop

Pipeloop is the Bun-native command-line runtime for the delivery skills in the a9/skills repository.

bunx pipeloop --help
bunx pipeloop issue --help
bunx pipeloop project --help
bunx pipeloop milestone --help
bunx pipeloop git flow --help
bunx pipeloop pr --help

The package executes TypeScript directly with Bun. It intentionally has no compile or build step.

Version 0.3.0 keeps Projects optional and automatically binds new Issues when a repository Project is available. It adds repository Project discovery and verifies membership and assigned fields before reporting success. Creation failures report the existing Issue and recovery command so users can repair binding without creating duplicates. Lifecycle commands verify Status before reporting success.

Project is optional. issue create and lifecycle commands use an explicit --project OWNER/NUMBER, an existing repository Project cache, or the repository's linked open Projects. No Project means normal Issue-only behavior with no extra flags. One linked Project is selected automatically; multiple Projects require a choice before any Issue mutation. A discovery failure is not treated as no Project. Pipeloop never creates a Project just to process an Issue.

When a Project is selected, issue create adds and verifies the new Issue before reporting success. It preserves Project defaults and accepts --field NAME=VALUE assignments, validated before creation. If creation succeeds but binding fails, the command reports the Issue number/URL and a project add recovery command; do not repeat creation. Milestone and Assignee rules remain repository-specific.

Issue lifecycle commands synchronize the selected Project's Status: plan, implement, and review set In Progress; close sets Done; reopen sets Todo. Pass --project OWNER/NUMBER to select a Project explicitly. The target Project must already provide these exact Status options. An Issue not yet on the selected Project is added using the existing Project operation.

Issue and Project changes are separate: a Project failure returns nonzero and reports the successful Issue change and a recovery command. A repeated lifecycle command still reconciles Project Status when the Issue labels already match. Success is printed only after remote readback and cache refresh. project add likewise verifies membership and all assigned fields before reporting success. No historical Issues are changed automatically.

On Windows, use bunx --bun pipeloop .... Verify the actual version/help and operation output. If bunx exits zero without running the CLI, use the reviewed source directly: bun <checkout>/apps/pipeloop/src/cli.ts .... An unpublished source fix is not available through the npm latest tag until separately released.