Skills your agents can run
Plug-and-play capabilities — vetted, versioned, and runnable from any Mighty agent.
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOs, and optionally bumps VERSION.
Manage the project's core principles and ensuring alignment. Create or update the project constitution from interactive or provided principle inputs.
Audit and improve CLAUDE.md files in repositories. Use when the user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs a quality report, then makes targeted updates. Also use when the user mentions “CLAUDE.md maintenance” or “project memory optimization.”
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Audit GitHub Actions workflow files for hardening gaps (missing timeouts/permissions/concurrency and floating action refs).
Create and deploy single-page static websites to GitHub Pages with an autonomous workflow. Use it when building portfolio sites, CV pages, landing pages, or any static web project that requires GitHub Pages deployment. It handles the complete workflow from project initialization to live deployment by provisioning a GitHub Actions pipeline for automation.
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures.
Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says 'linear', 'linear issue', or 'link linear', (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.
Manage Bitbucket repositories, pull requests, and pipelines via API.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
GitHub Actions integration. Manage data, records, and automate workflows. Use when the user wants to interact with GitHub Actions data.
Review working directory changes for code quality, security, and best practices before creating a PR. Use when: "review my code", "check before PR", "code review", "check before creating a PR".
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Fetch upstream, rebase, stage all changes, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream. Handles merge conflicts by preferring local changes for config/project files and upstream for scaffolding.
Git workflows, branching strategies, and hooks.