dotfiles

Create a demo user and company on local Panda via curl. Authenticates against the local dev server, submits the demo account form, and returns login credentials. Use when the user asks to create a local user, demo account, demo company, or needs a test account on local Panda.

Publish implementation plans to Notion instead of local markdown. Use whenever creating an implementation plan, architecture plan, spike plan, migration plan, or any planning document. Replaces local docs/ output with a Notion page under the Planning docs page.

List and remove old git worktrees sorted by last activity. Shows when each worktree was last touched and lets the user pick which ones to remove. Also cleans up the associated local branch and AVD emulator if one exists. Use when the user says "cleanup worktrees", "remove worktrees", "delete old worktrees", "clean up branches", or "list worktrees".

Delete all Android emulators created by the build-android-app skill. Finds AVDs matching the {project}_{branch} naming convention, shuts down any that are running, and deletes them. Use when the user says "cleanup emulators", "delete emulators", "remove avds", or "clean up android emulators".

Build, install, and launch an Android app on an emulator after code changes. Auto-detects Gradle wrapper, build variant, application ID, and emulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on emulator", or when a workspace rule says to build after changes.

Build, install, and launch an iOS app on the Simulator after code changes. Auto-detects project file, scheme, bundle ID, and simulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on simulator", or when a workspace rule says to build after changes.

Create, delete, and manage iOS Simulator devices using xcrun simctl. Use when the user wants to create a simulator, delete a simulator, list simulators, reset a simulator, clone a device, rename a device, or manage simulator lifecycle (boot, shutdown, erase).

Prepare code for commit with quality checks and conventional commit message generation. Use when the user asks to prepare a commit, review changes before committing, or wants a thorough pre-commit check including lint, tests, and code review.

Provides a map of all local projects, their tech stacks, dependencies, and inter-system relationships. Use when the user asks about project architecture, cross-repo dependencies, how systems connect, which repo owns what, or needs to explore another codebase. Also use when the user mentions Gusto, Guideline, Zenpayroll, mobile-app, mb-ios, mb-android, or asks "where does X live?"

Visually validate code changes by analyzing the git diff, identifying affected screens, and capturing screenshots via Maestro. Delegates to maestro-take-screenshots and maestro-explore skills. Use when the user says "validate change", "visual check", "screenshot my changes", "validate the app", or wants to see what their code changes look like on a device.

Create a GitHub pull request using the gh CLI. Analyzes all changes from main, generates a description following the PR template, and creates the PR if one doesn't exist. Reads .project-settings.md to determine whether the project uses Jira or GitHub Issues. Use when the user asks to create a PR, open a pull request, or submit changes for review.

Run the full ticket lifecycle end-to-end without manually triggering each step. Chains initialize, start-work, prepare-commit, create-pr, and review-pr in sequence. Supports autopilot (no prompts) or pair (interactive) mode. Use when the user says "full workflow", "end to end", "run the whole thing", or wants to go from ticket to reviewed PR in one go.

Start working on a ticket/issue by fetching details and creating a git branch in a new worktree. Reads .project-settings.md to determine target (Jira or GitHub). Use when the user wants to start a ticket, begin work on an issue, or create a branch for a task. For unticketed work, asks for a short description to build the branch name.

Create and configure git worktrees for parallel development. Use when the user wants to start a new worktree, work on multiple branches simultaneously, set up an isolated development environment, or mentions worktree.

Use when creating project tickets or issues (Jira or GitHub). Reads .project-settings.md to determine target system. Runs a three-step pipeline (research → write → publish) using the steps in this skill's steps/ directory.

Generate a release readiness report comparing the latest GitHub release with the Jira board's Merged column. Identifies tickets that need to be moved to Done. Use when the user asks for a release report, wants to check release status, asks what tickets need to be moved to Done, or says "release report".

Review GitHub pull requests using the gh CLI. Fetches PR diff and details, optional Jira or GitHub issue context from branch, analyzes for code quality, security, tests, and style, then posts inline comments. Use when the user asks to review a PR, check a pull request, or mentions a PR URL or number.

Start or resume work on a Jira ticket or GitHub issue by extracting the ID from the branch name, fetching requirements via Jira MCP or GitHub (gh/API), creating an implementation plan, and executing it. Use when the user wants to start ticket work, resume a ticket, implement requirements from Jira or a GitHub issue, begin coding on a branch, or mentions "start the ticket" or "execute the ticket".

Sync Cursor skills, agents, rules, and other dotfiles to chezmoi. Use when the user asks to update dotfiles (pull + apply), sync dotfiles, update chezmoi, or push dotfiles; or automatically after creating, editing, or deleting files in ~/.cursor/skills/, ~/.cursor/agents/, or ~/.cursor/rules/.

Take screenshots or record videos of specific pages and components in the mobile app using Maestro. Investigates existing test flows to learn navigation paths. Use when the user wants a screenshot, screen capture, visual snapshot, or video recording of a specific page, screen, component, or feature in the app.

Interactively create a Maestro E2E test flow by inspecting the live device screen and building the YAML step by step. Use when the user wants to create a new Maestro test, write a new E2E flow, build a test from the device, or says "create a maestro test" or "record a test flow".

Reference for writing and debugging Maestro E2E test flows. Covers all YAML commands, selectors, JavaScript integration, CLI usage, and flow structure. Use when writing Maestro tests, looking up command syntax, troubleshooting flow failures, or asking how to do something with Maestro.

Explore the mobile app to find a specific page, screen, or component by iteratively inspecting and navigating the live device via Maestro MCP. Use when the user wants to find something in the app, navigate to a screen, locate a component, explore the app, or says "find the X screen" or "how do I get to Y".

Run a Maestro E2E test, and if it fails, diagnose and fix it in a loop until it passes. Analyzes failure screenshots, failed steps, and device view hierarchy via Maestro MCP to determine root cause, applies fixes, and re-runs. Use when the user says "debug this test", "fix this maestro test", "why is this test failing", or wants to get a Maestro test passing.

Run the full push-and-PR flow for a simple change with no prompts after start. Collects files, ticket (or unticketed RETIRE-1908), and optional branch/commit message up front, then stages, lints, tests, commits, pushes, and creates the PR. Use when the user wants to push a change and open a PR in one go without interruption.

Run Maestro E2E tests from a file or directory path and capture output to a results directory. Use when the user wants to run a Maestro test, execute a test flow, run E2E tests with output, or mentions "maestro test" with a path.

Generate dependency diagrams from code or architecture. Traces code-level dependencies (hooks, queries, providers, components) or maps high-level system architecture. Outputs Mermaid diagrams in markdown or FigJam via Figma MCP. Use when the user asks to map dependencies, visualize relationships, create a dependency diagram, diagram an architecture, or trace how systems connect.

Investigate a codebase topic and produce structured markdown documentation. Collects investigation scope, explores the code, and writes a README plus sub-docs for each area. Use when the user asks to investigate, spike, research, analyze, or document how something works in the codebase.

Write or improve documentation using the Diataxis framework. Creates user-centered docs in four types - tutorials, how-to guides, reference, explanation. Use when writing docs, improving documentation, auditing docs, or when the user mentions Diataxis.

Document generator that produces polished markdown for any technical document - tickets, PR descriptions, spikes, plans, reports, architecture decisions, RFCs, and proposals. Use directly when the user asks to write, draft, or summarize a document or plan, or as the writing engine called by other skills (e.g. write-tickets for ticket markdown, dev-workflow-create-pr for PR body content).

Publish a ticket to JIRA using acli. Converts markdown to ADF, creates the ticket, and sets component/sprint. Called by write-tickets after ticket content is finalized in a temp file. Not intended for direct user invocation.

Forces the agent to always use the AskQuestion tool for user prompts instead of conversational questions. Apply this whenever asking the user anything - questions, confirmations, choices, or clarifications. Never ask conversational questions when structured options are possible.

Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.

Walk through PR review comments one by one, spawn a subagent per comment to validate the concern and propose fixes, then explain each to the user and suggest fixes without replying on GitHub. Use when the user wants to address PR feedback, go through review comments, process PR comments interactively, or respond to code review.

End-to-end test the mobile app using Maestro - includes smoke testing, full test suites, or targeted feature testing. Use when the user wants to smoke test, E2E test, run Maestro tests, test the app, verify critical paths, or check if the app works.

Fix all failing tests by running the test suite and spawning subagents to fix each failing test file. Use when the user asks to fix all tests, fix failing tests, or update tests to match current code.

Push git changes to remote with full workflow including status check, staging, committing, and pushing. Use when the user asks to push changes, push up code, or sync with remote. Includes safety check to prevent pushing directly to main branch.

Resolve git merge or rebase conflicts when syncing a branch with main. Use when the user asks to resolve conflicts with main, merge main, rebase on main, fix merge conflicts, sync with main, or update branch from main.

Search the web monorepo (../app) to find how web handles equivalent functionality. Use when implementing mobile features that need to match web behavior, finding web routes, or understanding how web handles a specific feature like statements, portfolios, or user flows.

Use when viewing, searching, or working with Jira issues/work items via acli. Provides command patterns for authentication, viewing issues, creating/editing work items, commenting, transitions, searching, bulk operations, and troubleshooting