CLI design guidelines — arguments, flags, subcommands, help, output, errors, interactivity, config precedence. Apply when designing new commands or reviewing CLI UX.
Skills（SKILL.md）は、AIエージェント（Claude Code、Cursor、Codexなど）に特定の能力を追加するための設定ファイルです。
詳しく見る →CLI design guidelines — arguments, flags, subcommands, help, output, errors, interactivity, config precedence. Apply when designing new commands or reviewing CLI UX.
Canonical GitHub issue execution route after plan approval — strengthened resource intelligence, TDD-first implementation, targeted validation, adversarial review, delegation controls for Claude agent teams, GitHub progress posting, future-issue capture, and commit/push with closeout discipline.
>-
Scans TypeScript/JavaScript source files to find files that still contain hardcoded, non-i18n text and outputs only the file paths. Use when auditing localization coverage, checking a directory, or reviewing a commit for missing i18n extraction.
Verifies that i18n replacements (t/i18n.t/Trans) in source code follow extract-i18n-keys rules and that keys exist in modules with correct English copy; also checks for over-extraction (content that should not have been extracted, e.g. URLs, class names, alt/aria-label/data-*, meta, technical strings). When given a commit or range, scopes verification to changed files and optionally checks that replaced text matches module values via diff. Use for PR/commit review, i18n audit, or post-replacement validation. Read-only.
Use when the user asks to commit, create a git commit, checkpoint changes, save work to git, or write a commit message.
Use when the user asks to reflect on recent sessions, analyze repeated mistakes, or review prompting and agent patterns for improvement.
Use when the user wants an independent expert review of work done in this conversation before accepting or extending it.
Use when creating, editing, or visually reviewing Pencil (.pen) screens, components, or flows.
Use when reviewing a pull request, merge request, or local diff for correctness, security, and code quality.
Use when the user asks to create or update a pull request for the current branch.
Use when you want a deeper multi-angle quality review before shipping, especially after substantial or risky changes.
Use when reviewing a user-facing page or flow for usability issues, confusion, friction, or missed UX principles.
Use when removing a git worktree and cleaning up its associated local branch from the main repository.
Use when asked to add or modify hooks for Claude Code specifically. Or, if the user is asking to automate an action, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
Deploy ServiceNow configuration changes safely — either via Update Sets (classic instances) or now-sdk install (Fluent SDK projects). Covers Update Set naming, parent/child batching, preview validation, and SDK build/install workflows. Use when managing releases, migrating between instances, promoting changes from dev to test to prod, or orchestrating complex deployments with multiple Update Sets. Trigger this skill whenever the user mentions deployment, Update Sets, moving changes between environments, release management, or now-sdk install.
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
セッション開始時にゴール・完了条件・タイムボックスを明確化する。作業セッションの冒頭で方向性を揃えるために使う。
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
PR 管理：浏览、摘要、创建、更新、查看 review 评论、回复 review。触发词：'pr'、'pull request'、'创建 PR'、'回复 review'。
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
Use when designing, reviewing, or refactoring a CLI that must serve AI agents alongside humans, or when converting an API or SDK into an agent-usable CLI interface.
**Purpose:** Execute multi-step workflows in a single transaction.
> Transforms any GitHub Pull Request into a beautiful, single-page interactive HTML course that teaches the problem, solution, and code changes.
Review Vue 3 code for Composition API, reactivity, components, state (Pinia), routing, and performance. Framework-only atomic skill; output is a findings list.
Merge one or more GitHub pull requests, especially when the user wants to merge multiple PRs in one batch. Use when Claude needs to inspect PR relationships, squash-merge by default, retry with --admin only when GitHub requires it, resolve conflicts against main or another base branch, and retarget or refresh dependent open PRs after earlier merges.
Wrap up current work: review + test + gates + commit in one operation. Use when user says 'ship', 'ship it', 'wrap up', 'done', 'finish', 'готово', 'отправляй', 'заверши', 'закрывай'.
Author-side self-review of code changes before requesting PR review. Use when the author wants to assess blast radius, convention compliance, and merge readiness of their own diff.
Spoke engineering conventions for implementation work including coding, testing, technical debt, design handoffs, and repo orientation. Use when actively building or reviewing code and you need developer guidance with platform guardrails.
This document shows how to build up a complete code review system using the simple tools specification and markdown-based agents.
| Agent | Tier | Model | Purpose |
- [Use-Case Quick Reference for This Section](#use-case-quick-reference-for-this-section)
Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, navigation patterns, performance optimization, and testing best practices.
Interact with GitHub using the `gh` CLI. Use when managing issues, PRs, workflow runs, or advanced API queries via `gh issue`, `gh pr`, `gh run`, and `gh api`.
>-
>
METAINFORMANT rules for directory scripts. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory scripts/ontology. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory examples/templates. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory examples/multiomics. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
lease-commercial
opinion-editorial
This skill should be used when users need to write, review, or debug Stata code for data cleaning and analysis. Use this skill for tasks involving data import, variable management, data documentation, merging/appending datasets, creating analysis variables, and following IPA/DIME Analytics coding standards. This skill should be invoked when working with .do files, .dta files, or any Stata-related data processing tasks.
METAINFORMANT rules for directory scripts/menu. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory src/metainformant/multiomics. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory config/amalgkit. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory scripts/simulation. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory scripts/gwas/structure. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory docs/multiomics. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.
METAINFORMANT rules for directory scripts/gwas/preparation. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.