ai-config

Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.

Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.

Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.

Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.

Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.

Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.

Add a GitHub Actions workflow that spins up a temporary Fly.io preview app per pull request, backed by a fork of the production Turso database, and destroys both on close. Use when: adding PR previews, review apps, per-PR deploy environments.

Create a new database on Turso, asking whether it goes in a new or existing database group, and wire credentials into .env. Use when: creating a Turso database, setting up libSQL storage, new turso db. Building block for create-website.

Append an accomplishment, framed as impact, to the Anytype page titled "Impact Log" for perf reviews and promo packets. Use when: logging an accomplishment, updating the impact log, recording impact, capturing what I shipped this week.

Break a large initiative into sequenced, independently-shippable tickets and milestones. Use when: decomposing an epic, breaking down a large project, planning a multi-ticket initiative, sequencing work across milestones.

Map an unfamiliar repo or subsystem fast: entry points, data flow, key abstractions, and where to make a change. Use when: onboarding to a codebase, understanding unfamiliar code, getting oriented in a new repo or subsystem, figuring out how something works.

Sequence a large, multi-step refactor into small, independently-shippable, green-to-green steps behind a test safety net. Use when: planning a big refactor, restructuring a module safely, breaking a risky change into steps, migrating a pattern across a codebase.

Author a technical design doc / RFC from a problem statement or Jira ticket, grounded in the actual codebase. Use when: writing a design doc, drafting an RFC, proposing a technical approach, documenting a system design before building.

Scaffold a new skill in this ai-config repo: create the SKILL.md, update the README table and mermaid diagram, then run setup. Use when: adding a new skill, creating a skill, scaffolding a SKILL.md in this repo.

Create a git worktree with a lane/TICKET-description or lane/description branch name. Use when: creating a new worktree, spinning up a new branch workspace.

Review recent skill usage and suggest concrete improvements based on issues, workarounds, or friction encountered. Use when: a skill did not work as expected, after completing a workflow, refining skill instructions.

Remove a git worktree and clean up its directories. Use when: removing a worktree, cleaning up a finished branch workspace.

Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.

Fetch a Jira ticket via the Atlassian MCP and summarize its intent and acceptance criteria. Use when: reading a Jira ticket, pulling ticket context, looking up a ticket's details, getting acceptance criteria. Building block for other skills that need ticket context.

Produce a concrete coding plan from a Jira ticket or a plain description: file locations, implementation steps, and edge cases. Use when: planning work, breaking down implementation, figuring out where to start coding.

Resolve a GitHub pull request (from a link, number, or the current branch) and fetch its details, diff, and review threads. Use when: looking up a PR, pulling PR context, fetching a pull request and its comments. Building block for other skills that operate on a PR.

Review a GitHub pull request from a link or PR number, using the linked Jira ticket and PR body for context. Use when: reviewing a PR, giving feedback on a pull request, code review of someone else's PR, looking over a PR.

Start work on a new task: read a Jira ticket, create a git worktree with a properly named branch, produce a coding plan, and move the ticket to In Progress. Use when: starting a new task, picking up a ticket, beginning a feature, start work, new worktree.

Transition a Jira issue to a new status using MCP tools. Use when: moving a ticket to In Progress, In Code Review, Done, or any other status.

Generate tests for a file or function. Use when: adding tests to untested code, improving test coverage, writing unit tests, writing integration tests, testing a new feature.

Summarize GitHub notifications and open PRs into a prioritized daily work list. Use when: planning the day, checking what needs attention, morning standup prep, what should I work on.

Craft a conventional commit message from staged changes, get user approval, then commit and push. Use when: writing a commit message, committing staged changes, pushing a commit.

Open a GitHub pull request for the current branch. Use when: opening a PR, creating a pull request, submitting code for review.

Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work.