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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Creates GitHub issues with proper context using gh issue create and the repository's issue templates.
Use AskUserQuestion to select:
Read project metadata before creating the issue:
# Version
grep "^version=" gradle.properties
# Kotlin version
grep "^kotlin " gradle/libs.versions.toml
# Current branch and recent changes
git branch --show-current
git log --oneline -5
Title prefix: [Bug]: . Auto-labels: bug, needs-triage.
Template fields (from .github/ISSUE_TEMPLATE/bug_report.yml):
gradle.properties)libs.versions.toml)gh issue create \
--title "[Bug]: {description}" \
--label "bug,needs-triage" \
--body "$(cat <<'EOF'
### Fakt Version
{version}
### Kotlin Version
{kotlinVersion}
### Platform
{platform}
### Bug Description
**What's happening:**
{description}
**Steps to reproduce:**
1. ...
**Code example:**
```kotlin
// minimal reproduction
Error/build logs:
{logs}
EOF )"
#### Feature Request
The repository has no feature-request issue template and blank issues are disabled: `.github/ISSUE_TEMPLATE/config.yml` routes ideas to GitHub Discussions (Ideas category). Point the user there; if they want a tracked issue instead, create it as a Task/chore.
#### Task/Chore
No template required (internal use). Use conventional title format.
```bash
gh issue create \
--title "{type}: {description}" \
--label "{labels}" \
--body "$(cat <<'EOF'
## Context
{context}
## Scope
{scope}
## Checklist
- [ ] {step1}
- [ ] {step2}
EOF
)"
Auto-applied by templates:
bug + needs-triage (bug reports)enhancement + needs-triage (feature requests)Category labels:
compiler, gradle-plugin, documentation, performance, testing, ci/cdPriority labels:
priority: high, priority: medium, priority: lowContributor labels:
good first issue, help wanted, needs-investigation, needs-discussionLifecycle labels:
idea, approved, breaking-change, dependencies, securityNote: Category and lifecycle labels must exist in the repository before use. Run
gh label listto check available labels, orgh label createto add missing ones. Onlybug,enhancement, andneeds-triageare auto-created by issue templates.
When the issue relates to specific code, gather relevant context:
# Find affected files
# Read error messages from recent builds
# Check if related issues exist
gh issue list --label "{label}" --state open
Include file paths, function names, and module affected in the issue body.
Note: GitHub issue templates use YAML form schema. When creating via
gh issue create --body, the structured fields render as markdown headers in the created issue.
After creating the issue, display:
pr — analogous GitHub creation workflowcompilation — provides error context for bug reports아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks Kotlin compiler API usage against the Kotlin versions Fakt supports — which path runs on which compiler, how compat shims are written, how to verify across versions, and how to bump Kotlin. Use when calling a new FIR/IR/compiler-plugin API, seeing NoSuchMethodError, NoSuchFieldError or NoClassDefFoundError from compiler classes, bumping the Kotlin version, or checking whether an API exists in the minimum supported Kotlin. Make sure to use this skill whenever compiler plugin code starts using a Kotlin compiler API it didn't use before — these APIs change between Kotlin releases and a break only shows up on an older supported version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.