basecamp

Address PR review comments - fix issues, reply to threads, mark resolved

Explicitly launch an independent outside-expert consultation via Codex. Use only when the user directly asks to run this workflow or asks another expert/agent for an independent second opinion. Do not infer it from ordinary review, feedback, validation,…

Explicitly launch the automated Ralph-Lisa plan-implement-review workflow. Use only when the current request directly asks to start or run Ralph-Lisa; a mention or discussion of the skill is not an invocation. Never infer it from ordinary planning, building,…

Fetch git log from local repos into day-cached JSON atoms. Simplest activity fetcher — no API calls, no pagination. Part of the recap plugin's activity fetcher pipeline.

Use when resolving zizmor warnings in GitHub Actions workflows, hardening CI pipelines, or pinning actions to SHA hashes. Covers artipacked, template-injection, excessive-permissions, secrets-outside-env, dependabot-execution, and when to suppress vs fix.…

Write, slim, or audit a repository's agent instruction file — AGENTS.md, CLAUDE.md, or similar. Use when creating one for a repo that lacks it, when an existing one has grown bloated, stale, or contradictory, or when reviewing one for wrong commands and dead…

Use when sweeping a whole dependency corpus or codebase for every instance of one known bug class — "audit our gems/modules/packages for X", "we fixed this here, where else does it occur?", "find every place this pattern appears". Truffle hunting. Covers…

Use when a Ruby native extension segfaults intermittently, corrupts data under load, or breaks after GC.compact — and when auditing native gems for dangling pointers. The scent library for use-after-free and GC-invalidated pointers in C extensions: raw VALUEs…

Verify a Rails-to-Rust migration using HTTP, browser, persisted-state, cookie, job and realtime comparisons. Use when implementing or reviewing compatibility evidence, not ordinary app tests.

Inventory a Rails application for a Rust port, including implicit framework contracts, legacy dependencies and release constraints. Use before choosing the migration architecture or splitting implementation areas.

Measure and simplify a Rails-to-Rust port using comparable production workloads and before/after evidence. Use for benchmark tables, profiling, dependency cuts or connection-capacity estimates.

Convert Rails applications into Rust using a pinned running reference, compatibility contracts, generators and parity evidence. Use for planning or carrying out a migration, not ordinary Rust feature work.

Prepare deployment and rollback for a compatible Rust replacement of a Rails app. Use for release gates, staging checks, old-session continuity and an authorized cutover, not general feature implementation.

Capture Rails and Ruby compatibility contracts from an application’s actual pinned runtime for a Rust migration. Use for golden vectors, live schema/routes, cookie continuity and reference fixture setup.

Implement Rails application behavior in Rust against captured reference contracts, including transactions, controllers, templates, assets, jobs and integrations. Use during a migration’s implementation phase.

Prepare deployment and rollback for a compatible Elixir replacement of a Rails app. Use for release gates, staging checks, old-session continuity and an authorized cutover, not general feature implementation.

Inventory a Rails application for a Elixir port, including implicit framework contracts, legacy dependencies and release constraints. Use before choosing the migration architecture or splitting implementation areas.

Capture Rails and Ruby compatibility contracts from an application’s actual pinned runtime for a Elixir migration. Use for golden vectors, live schema/routes, cookie continuity and reference fixture setup.

Verify a Rails-to-Elixir migration using HTTP, browser, persisted-state, cookie, job and realtime comparisons. Use when implementing or reviewing compatibility evidence, not ordinary app tests.

Measure and simplify a Rails-to-Elixir port using comparable production workloads and before/after evidence. Use for benchmark tables, profiling, dependency cuts or connection-capacity estimates.

Implement Rails application behavior in Elixir against captured reference contracts, including transactions, controllers, templates, assets, jobs and integrations. Use during a migration’s implementation phase.

Convert Rails applications into Elixir using a pinned running reference, compatibility contracts, generators and parity evidence. Use for planning or carrying out a migration, not ordinary Elixir feature work.

Bug reproduction for the Lexxy rich text editor. Core editing bugs use Playwright (Selenium fallback); system-level bugs use Capybara. All local.

Process multiple bugs from a Fizzy board (or GitHub issues) in parallel. Uses worktree agents to reproduce, fix, test, create PRs, and comment on cards.

Validate a bug-fix PR by reproducing the bug in production and confirming the fix locally, using browser automation.

Drive your own Claude Code session from Basecamp. Starts the local connector (basecamp connect), which listens to the account's event feed as a Basecamp agent and prints one line per trusted request: a mention, an assignment, a comment on a thread the agent…

Interact with Basecamp through the Basecamp CLI. Use for any Basecamp question or action, including projects, todos, cards, messages, files, schedules, check-ins, people, assignments, notifications, search, and account settings.

Diagnose Basecamp CLI, authentication, and agent-plugin health.

Interact with HEY via the HEY CLI. Read and send emails, manage contacts, boxes, labels, collections, calendars, todos, habits, time tracking, and journal entries. Use for ANY HEY-related question or action.

Diagnose Basecamp CLI, authentication, and agent-plugin health.

Interact with HEY via the HEY CLI. Read and send emails, manage contacts, boxes, labels, collections, calendars, todos, habits, time tracking, and journal entries. Use for ANY HEY-related question or action.

Interact with Fizzy via the Fizzy CLI. Manage boards, cards, columns, comments, steps, reactions, tags, users, notifications, pins, webhooks, and account settings. Use for ANY Fizzy question or action.

Check upstream Basecamp API changes and sync the Smithy spec. Compares bc3 API docs and app code against the tracked bc3 revision in spec/api-provenance.json, identifies what changed, and optionally updates the Smithy spec and regenerates SDKs.

Manage local Claude Code agents from Basecamp. Runs the connector bridge (bin/connect), watches its STDOUT for trusted events — authored by an authorized user (the operator alone, by default) and @mentioning a real Basecamp agent user — acknowledges each as…

Work with Basecamp through the Basecamp tools — find, read, create, and update projects, to-dos, cards, messages, comments, documents, schedules, and Campfire chats. Use for any Basecamp question or action, and for any basecamp.com link.

Audit a Go CLI against the 37signals CLI rubric