[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use Conventional Commits format: <type>: <short description>
| Type | When to use |
|---|---|
feat: | New feature or contract |
fix: | Bug fix |
refactor: | Code restructure without behavior change |
test: | Add or update tests |
docs: | Documentation changes |
chore: | Build config, dependency updates, toolchain |
security: | Security fix or hardening |
git diff to review all changes before staginggit add . to prevent committing .env or artifactsCo-Authored-By lines — commit messages should only contain the descriptiongit push unless explicitly requested| Pattern | Example |
|---|---|
feat/<name> | feat/staking-pool |
fix/<name> | fix/reentrancy-guard |
refactor/<name> | refactor/token-structure |
Every PR must include:
| Section | Content |
|---|---|
| Change description | What was changed and why |
| Test results | forge test output (all pass) |
| Gas impact | forge test --gas-report diff for changed functions |
| Deployment impact | Does this affect deployed contracts? Migration needed? |
| Review focus | Specific areas that need careful review |
| Scenario | Requirement |
|---|---|
| Standard changes | Minimum 1 maintainer approval |
| Security-related changes | Minimum 2 maintainer approvals |
| AI-generated code | Must pass manual review + forge test before merge |
| Contract upgrades | Requires full team review + upgrade simulation on fork |
forge test before committingforge fmt after AI generates code to ensure consistent formattingまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
日本語の概要は準備中です。原文の説明を表示しています。
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
日本語の概要は準備中です。原文の説明を表示しています。
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
日本語の概要は準備中です。原文の説明を表示しています。