Script and automate repetitive tasks and workflows.
Autonomously completes Linear tickets via git worktrees. Use when user says "fix ENG-123", "complete LIN-456", "work on linear ticket", provides a linear.app URL, or mentions a ticket ID pattern like ABC-1234. Creates git worktree, implements fix via autonomous planning/review loop, opens GitHub PR with full reasoning.
Standards pour les commits Git. Use when "commit", "git commit", "commit message", "prepare commit".
Generate or update GitHub Pull Request titles and descriptions based on actual code changes in the final state. Use when the user mentions updating, generating, or writing PR descriptions, PR titles, pull request summaries, or says 'update the PR'. Analyzes git diff to determine what's actually in the code (not just commit history) and creates comprehensive, accurate PR documentation.
Load when starting work in 10x-Mapmaster or when unsure about project standards. Covers file organization, naming conventions, type constraints, SQL style, and project-specific limits (200-char descriptions, answer enums). Use to understand how the codebase is structured and what standards to follow.
Use when reviewing code changes or conducting PR reviews.
Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality, tests pass, and documentation is updated. Triggers on "commit", "stage changes", "ready to commit", or when completing a feature or fix.
Automatically sync with GitHub at session start and remind Claude to push/pull changes as it works. Triggers on session start, reactivation, or when working in git repositories.
Analyzes git changes and generates commit messages. MUST use proactively after completing any implementation task, bug fix, or refactoring. Also triggers on "commit", "コミット".
View and analyze commits in GitHub repositories - commit history, diffs, and commit details using gh CLI
Review and improve repository documentation including both human-readable docs (`docs/`), `README.md`, and AI agent memory context files (`CLAUDE.md`, `CODEX.md`, `AGENTS.md`, `.cursorrules`, etc.) for clarity, minimal duplication, and modularity. Use when asked to review, audit, refactor, or improve documentation structure, consolidate rules, reduce redundancy, establish shared standards, or modularize monolithic instruction files.
This skill should be used when the user asks about "snapshot.md", "constraints.md", "decisions.md", "debt.md", ".ctx/", "living context", "documentation freshness", "stale docs", "ADR", "architecture decision", "technical debt", "system context", "co-located documentation", "context health", "validation", or needs help managing co-located documentation that stays synchronized with code.
Remove AI-generated code slop from a branch. Use to delete unnecessary comments/docs, defensive checks, broad try/catch blocks, type-cast hacks, lint suppressions, dead code, duplication, and style drift. Diff against base (main/master) and align changes with existing project idioms without altering intended behavior.
Automated code review checklist. Use when reviewing PRs or code changes.
Review code and PRs. Use when reviewing pull requests, code changes, or providing feedback.
Your approach to handling global justfile. Use this skill when working on files where global justfile comes into play.
Set up btca (Better Context) in a project by scanning dependencies, proposing resources, creating btca.config.jsonc, updating AGENTS.md, and explaining usage modes. Use when asked to configure btca/better-context for a repo.
Manage the PR review feedback loop: monitor CI checks, fetch review comments, and iterate on fixes. Use when: (1) pushing changes to a PR and waiting for CI/reviews, (2) user says "new reviews available", (3) iterating on PR feedback from Gemini, Cursor, Claude, or other reviewers, (4) monitoring PR status. Supports multiple review bots: Gemini Code Assist, Cursor Bugbot, and Claude agent fallback. Automatically detects priority levels from different bot formats and handles rate limits. RECOMMENDED: Spawn a Task agent (subagent_type: general-purpose) to execute the review loop autonomously. See "Recommended Usage: Run as Task Agent" section for the prompt template. CRITICAL: When using this skill, NEVER use raw git commit/push commands. ALWAYS use commit-and-push.sh script. The user has NOT granted permission for raw git commands - only the script is allowed.
Guidelines for writing clean, professional code. Use when writing or modifying code, creating commits, or generating code comments. Ensures code is written for team consumption without conversation artifacts.
Generate comprehensive pull request descriptions that help reviewers understand code changes. Use when the user asks to "generate PR description", "create PR summary", "write PR intro", or needs help documenting their code changes for review. Analyzes git diffs or specified files to create structured descriptions covering why changes were made and what was implemented.
This skill should be used when the user asks to "commit", "create a commit", "make a commit", "git commit", "commit these changes", or wants to stage and commit changes to git. Handles staging files, drafting commit messages, following commit conventions, and managing git commits safely.
Standardize git commit messages using a consistent convention and guide clean-history workflows. Use when a user asks for commit message suggestions, to enforce a commit style, or to keep history clean by amending small fixes to the previous commit.
Comprehensive guide for writing effective git commit messages with support for multiple conventions (Conventional Commits, Semantic Commits, Japanese practices). Use when: (1) Creating git commits - generate or validate commit messages, (2) Reviewing commit messages - suggest improvements based on best practices, (3) Setting up commit message guidelines for a project, (4) User explicitly asks about commit message conventions or best practices. Supports both English and Japanese commit messages.
