tranquilo-maintainer

star 1

Use when modifying the Tranquilo repo, release automation, CLI/MCP surfaces, installers, or shipped agent assets.

f0rr0 By f0rr0 schedule Updated 4/22/2026

name: tranquilo-maintainer description: Use when modifying the Tranquilo repo, release automation, CLI/MCP surfaces, installers, or shipped agent assets.

Tranquilo Maintainer

Use this skill when working inside the Tranquilo repository.

Required Workflow

  • Run auth_status only when testing live Tranquilo behavior; do not require live credentials for release or packaging work.
  • Add a Changesets file for every change that should ship in the next CLI binary release: CLI behavior, MCP tools, shipped agent assets, or release target metadata.
  • Do not add a CLI Changesets file for site/docs-only changes. Those can deploy without creating a new CLI release.
  • CLI releases are manual. After merging release-worthy changes to main, run the release workflow from the GitHub Actions panel on the main branch.
  • Use an explicit no-release Changesets file only when Turbo affected reports the tranquilo workspace but the PR should not bump the CLI.
  • Never hand-edit generated release sections in CHANGELOG.md; add or update .changeset/*.md instead.
  • Fumadocs content is committed source under packages/docs-content: meta.json, versions/**, llms.txt, and skill.md. Generated docs are written directly to exact versions/vX.Y.Z paths so the public switcher only shows numbered CLI versions.
  • Use conventional commit messages that pass commitlint, such as feat: add release packaging or fix: repair PR install route.
  • Keep Lefthook pre-commit, commit-msg, and pre-push hooks aligned with CI. Pre-push should include the changeset gate, build, release smoke, and actionlint.
  • Keep packages/cli-model/src/agent-catalog.ts as the source of truth for MCP tool metadata, agent-safe CLI commands, public docs, API boundaries, and shipped agent assets. Keep site-only install/download route behavior in packages/site-model so Turbo affected can distinguish site-only changes from CLI release changes.
  • Do not hand-edit generated docs, site metadata, skill references, Claude commands, or MCPB manifests. Fumadocs content is committed after generation; run bun run generate and include the resulting packages/docs-content changes. Ignored agent and site artifacts are still regenerated by bun run generate, bun run dev:*, bun run build, and bun run check.
  • Use @anthropic-ai/mcpb only for MCPB init/pack workflows. It does not solve drift between MCP tools, skills, manifests, and docs; the catalog generator does.
  • Never document unsafe agent flows: access/refresh token entry in chat, payment details in chat, payment app opening, direct coupon/cancel/reschedule calls, or background checkout creation from watches. Phone OTP entry is allowed only for the explicit Tranquilo login flow through auth_login_start and auth_login_verify.

Validation

Run these before handing off release or install changes:

bun run check
bun run generate
bun run actions:lint
bun run knip:check
bun run typecheck
bun run test
bun run build
bun run release:verify

For PR release testing, use the generated Vercel PR install URL after the preview artifact workflow completes.

Install via CLI
npx skills add https://github.com/f0rr0/tranquilo --skill tranquilo-maintainer
Repository Details
star Stars 1
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator