adalloul0928/developer-workflows

Query Doppler live through its CLI for projects, configs, and secret NAMES — never values. Use when you need to know what actually exists in Doppler right now — whether a variable is defined in a given project/config, which configs a project has, why one config works and another does not, why a doppler-wrapped MCP or command fails to start, or to check the env-topology map against reality. Works in CI, headless, and non-Claude clients. Names only; never print, fetch, or echo a secret value.

Authoritative map of how env vars and secrets flow across Doppler, Supabase, Vercel, EAS, GitHub Actions, and local .env files for PUMPD (mobile, backend, CI), the IAWIS store, and agent-tooling MCPs. Use when deciding where to set or find a variable, when a variable is undefined at runtime or build time, when wiring CI or EAS environments, or before answering any question about secret or env-var placement.

Triage MCP servers that are configured but not usable, and emit the exact command to fix each one. Use at the start of a session, when an MCP tool is unexpectedly missing, when a server reports needing authentication or fails to start, after adding a server, or before relying on a connector in a scheduled or headless run. Distinguishes needs-authentication from pending-approval from a broken launch wrapper, because the fixes are unrelated.

Confirm that the shared agent-tooling synchronization flow delivered the latest Developer Workflows skill. Use when the user asks to verify a post-sync skill availability or marketplace refresh. Do not use for production application validation.

Safely prepare the current Git branch or worktree for handoff by rebasing it onto the latest remote preview branch, creating or updating a succinct branch document with dated revisions, verifying the rebased result, and pushing to the existing upstream branch or a friendly new remote branch. Use when the user says "rebase this worktree on preview and push it", "update, document, and push this branch", or "prepare this branch for handoff". This workflow rewrites and publishes Git history; do not use it for read-only status checks, documentation-only edits, or direct work on preview or main.

Author a new Agent Skill and publish it to the agent-tooling repository so both Claude and Codex pick it up. Use when the user says "let's make a skill", "turn this into a skill", "capture this as a reusable workflow", or describes a repeatable procedure they want available in future sessions. Interviews for the name and trigger phrasing, checks for name collisions across owned and vendor skills, writes one portable SKILL.md into the right plugin bundle, adds native Claude and Codex adapters plus catalog entries when a new bundle is needed, validates against the repository contract, opens a pull request with auto-merge, then reports the per-client refresh required to consume it. Needs a repository checkout, a shell, and git.

Refresh the shared agent-tooling marketplace and installed Developer Workflows plugin for both Codex and Claude Code. Use when the user asks to sync agent tools, pull the latest shared skills, refresh developer workflows, or make a newly merged agent-tooling skill available locally. Do not use for creating new skills or updating a project-specific skill.

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use only when the user explicitly requests a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

Confirm that the shared agent-tooling marketplace updated successfully. Use when the user asks to test skill synchronization, verify a marketplace skill update, or check whether a newly published workflow is available. Do not use for project-specific application testing.

Bring a fresh git worktree to a runnable state — detect the package manager per directory, run the right install, and materialize env vars from their real source instead of copying a .env. Use when a new or existing worktree fails with missing modules, an undefined env var, a wrong Supabase target, or right after creating a worktree with git worktree add or wtp. Covers npm, pnpm, and deno surfaces in one checkout.