@bensandee/tooling 0.33.0 → 0.35.0

package/README.md

@@ -32,7 +32,7 @@ The tool auto-detects project structure, CI platform, project type, and Docker p
 | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `tooling repo:sync [dir]`         | Detect, generate, and sync project tooling (idempotent). First run prompts for release strategy, CI platform (if not detected), and formatter (if Prettier found). Subsequent runs are non-interactive. |
 | `tooling repo:sync --check [dir]` | Dry-run drift detection. Exits 1 if files would change. CI-friendly.                                                                                                                                    |
-| `tooling checks:run`              | Run project checks (build, docker:build, typecheck, lint, test, format, knip, tooling:check, docker:check). Flags: `--skip`, `--add`, `--fail-fast`.                                                    |
+| `tooling checks:run`              | Run project checks (build, docker:build, typecheck, lint, test, format, knip, tooling:check, docker:check). Flags: `--skip`, `--add`, `--fail-fast`, `--verbose`.                                       |
 
 **Flags:** `--yes` (accept all defaults), `--no-ci`, `--no-prompt`, `--eslint-plugin`
 
@@ -60,13 +60,13 @@ The generated `ci:check` script defaults to `pnpm check --skip 'docker:*'` since
 
 ### Release management
 
-| Command                          | Description                                                                                                                     |
-| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| `tooling release:changesets`     | Changesets version/publish for Forgejo CI. Flag: `--dry-run`. Env: `FORGEJO_SERVER_URL`, `FORGEJO_REPOSITORY`, `RELEASE_TOKEN`. |
-| `tooling release:simple`         | Streamlined release using commit-and-tag-version. Flags: `--release-as`, `--first-release`, `--prerelease`.                     |
-| `tooling release:trigger`        | Trigger a release workflow.                                                                                                     |
-| `tooling forgejo:create-release` | Create a Forgejo release from a tag.                                                                                            |
-| `tooling changesets:merge`       | Merge a changesets version PR.                                                                                                  |
+| Command                          | Description                                                                                                                                   |
+| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tooling release:changesets`     | Changesets version/publish for Forgejo CI. Flags: `--dry-run`, `--verbose`. Env: `FORGEJO_SERVER_URL`, `FORGEJO_REPOSITORY`, `RELEASE_TOKEN`. |
+| `tooling release:simple`         | Streamlined release using commit-and-tag-version. Flags: `--release-as`, `--first-release`, `--prerelease`, `--verbose`.                      |
+| `tooling release:trigger`        | Trigger a release workflow.                                                                                                                   |
+| `tooling forgejo:create-release` | Create a Forgejo release from a tag.                                                                                                          |
+| `tooling changesets:merge`       | Merge a changesets version PR.                                                                                                                |
 
 #### `release:simple`
 
@@ -147,7 +147,7 @@ To give individual packages a standalone `image:build` script for local testing:
 }
 ```
 
-**Flags:** `--package <dir>` (build a single package)
+**Flags:** `--package <dir>` (build a single package), `--verbose`
 
 #### `docker:publish`
 
@@ -157,7 +157,7 @@ Tags generated per package: `latest`, `vX.Y.Z`, `vX.Y`, `vX`
 
 Each package is tagged independently using its own version, so packages in a monorepo can have different release cadences. Packages without a `version` field are rejected at publish time.
 
-**Flags:** `--dry-run` (build and tag only, skip login/push/logout)
+**Flags:** `--dry-run` (build and tag only, skip login/push/logout), `--verbose`
 
 **Required CI variables:**
 
@@ -188,6 +188,17 @@ Available override fields:
 | `projectType`        | string  | Auto-detected from `package.json` deps                                           |
 | `detectPackageTypes` | boolean | `true`                                                                           |
 
+## Debug logging
+
+All CLI commands support a `--verbose` flag for detailed debug output. Alternatively, set `TOOLING_DEBUG=true` as an environment variable — useful in CI workflows:
+
+```yaml
+env:
+  TOOLING_DEBUG: "true"
+```
+
+Debug output is prefixed with `[debug]` and includes exec results (exit codes, stdout/stderr), compose configuration details, container health statuses, and retry attempts.
+
 ## Library API
 
 The `"."` export provides type-only exports for programmatic use: