Creates draft pull requests from the project PR template with Conventional Commits titles and an AI attribution footer. Use when creating or opening pull requests, running /pr, pushing a branch for review, or preparing changes for merge. Make sure to use this skill whenever a pull request needs to be created — it is the project's PR workflow and replaces the default one.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Creates pull requests — always as drafts, from the project template, crediting AI co-authorship.
# Current branch
git branch --show-current
# Verify not on main/master
git branch --show-current | grep -E '^(main|master)$' && echo "ERROR: Cannot PR from main"
# Check remote tracking
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null || echo "No upstream"
# Commits vs main
git log main..HEAD --oneline
# Changed files
git diff main..HEAD --stat
Block if:
Determine type from files:
feat — New functionalityfix — Bug fixesdocs — Only .md, docs/ changesrefactor — Restructure, same behaviortest — Test files onlybuild — build.gradle.kts, Makefile, CIchore — MaintenanceDetermine scope from paths: use the scope table in the commit skill (compiler, codegen, gradle, annotations, samples, claude, ci).
<type>[(scope)]: <description>
cat .github/pull_request_template.md
Fill template with analysis from step 2.
When Claude wrote or co-wrote the change, end the description with an attribution line after the template:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
If the session already supplies attribution lines for pull requests, use those verbatim instead. Keep the title free of attribution.
# Push branch
git push -u origin $(git branch --show-current)
# Create draft PR (if `gh` isn't available, use the session's GitHub tool with the same draft, title and body)
gh pr create \
--draft \
--title "<title>" \
--body "$(cat <<'EOF'
<populated template>
EOF
)"
PR CREATED (Draft)
URL: {url}
Title: {title}
To mark ready: gh pr ready {number}
To view: gh pr view {number} --web
Not on feature branch:
PR BLOCKED — Cannot create PR from main/master
Create a feature branch first: git checkout -b feat/your-feature
No commits:
PR BLOCKED — No commits ahead of main
Title too long:
PR BLOCKED — Title exceeds 72 characters (currently: {n})
Suggested: "{shortened}"
commit — Clean commits before PRbdd-test-runner — Run tests before PRまだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Runs BDD-compliant GIVEN-WHEN-THEN tests, validates naming compliance, and analyzes coverage. Use when running tests, checking BDD compliance, validating test patterns, or verifying that test names follow GIVEN-WHEN-THEN conventions. Make sure to use this skill whenever tests need to be executed — it validates naming compliance and catches convention violations that plain test runners miss.
日本語の概要は準備中です。原文の説明を表示しています。
Documents the Fakt code generation pipeline — immutable AST model, builder DSL, renderer, default value strategies, and extension functions. Use when modifying code generation, changing generated output, adding new generated patterns, understanding builders or renderers, adding a new default value strategy, or debugging generated output. Make sure to use this skill whenever generated Kotlin code needs to change — the pipeline has strict conventions (immutable AST, builder DSL, renderer separation) that must be followed even for small changes.
日本語の概要は準備中です。原文の説明を表示しています。
Creates project commits — Conventional Commits format, message quality (72 char subject, 80 char body), staged-change checks, and the AI co-author trailer. Use when committing changes, running /commit, creating commit messages, or reviewing commit message quality. Make sure to use this skill whenever a git commit is being created — it is the project's commit workflow and replaces the default one.
日本語の概要は準備中です。原文の説明を表示しています。
Validates compilation of generated Fakt fakes and diagnoses build failures — where fakes are generated, which path produced them, error classification, and root cause analysis. Use when compilation fails, generated code has errors, no fakes were generated, validating changes compile before committing, or checking if generated code is valid. Make sure to use this skill whenever a build error mentions generated fakes or the Fakt plugin — even if the root cause might be elsewhere, this skill's error classification pinpoints the actual source.
日本語の概要は準備中です。原文の説明を表示しています。
Guides step-by-step through all 11 touchpoints for adding a new @Fake annotation option (like mutability or callHistory). Covers annotation enum, CLI processor, Gradle plugin, FIR metadata, FIR translator, the shared FakeDeclaration model, and code generators. Use when adding a new option to @Fake, adding a new enum to the annotation, making something configurable per-interface, implementing a new compiler plugin feature flag, adding a new Gradle extension property, or extending the three-tier resolution (annotation → plugin → default). Make sure to use this skill whenever a change touches more than one layer of the option pipeline, even for small additions like a new enum value.
日本語の概要は準備中です。原文の説明を表示しています。
Creates well-structured GitHub issues using gh CLI with auto-detected project context (version, platform, module). Supports bug reports, feature requests, and internal tasks following repo templates. Use when creating a GitHub issue, reporting a bug, requesting a feature, logging a task, documenting a TODO as an issue, or recording a bug found during development. Make sure to use this skill whenever an issue needs to be created — it auto-detects project context and applies the correct template.
日本語の概要は準備中です。原文の説明を表示しています。