Skip to content
cccskills
FreePublished on GitHub

issue-creator

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67 stars(GitHub 67 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Issue Creator

Creates GitHub issues with proper context using gh issue create and the repository's issue templates.

Instructions

1. Determine Issue Type

Use AskUserQuestion to select:

  • Bug report — something broken, unexpected behavior
  • Feature request — new capability or enhancement (goes to Discussions, see below)
  • Task/chore — internal work, refactoring, documentation

2. Auto-Detect Project Context

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

3. Create Issue by Type

Bug Report

Title prefix: [Bug]: . Auto-labels: bug, needs-triage.

Template fields (from .github/ISSUE_TEMPLATE/bug_report.yml):

  • Fakt Version (auto-detected from gradle.properties)
  • Kotlin Version (auto-detected from libs.versions.toml)
  • Platform — KMP / JVM only / Android only
  • Gradle Version (optional)
  • KMP Targets (optional, if KMP)
  • Module Setup — Single-module / Multi-module
  • Bug Description — structured: what's happening, steps to reproduce, code example, error logs
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
)"

4. Available Labels

Auto-applied by templates:

  • bug + needs-triage (bug reports)
  • enhancement + needs-triage (feature requests)

Category labels:

  • compiler, gradle-plugin, documentation, performance, testing, ci/cd

Priority labels:

  • priority: high, priority: medium, priority: low

Contributor labels:

  • good first issue, help wanted, needs-investigation, needs-discussion

Lifecycle labels:

  • idea, approved, breaking-change, dependencies, security

Note: Category and lifecycle labels must exist in the repository before use. Run gh label list to check available labels, or gh label create to add missing ones. Only bug, enhancement, and needs-triage are auto-created by issue templates.

5. Add Context from Codebase

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.

6. Output

After creating the issue, display:

  • Issue URL
  • Issue number
  • Labels applied
  • Assigned template

Related Skills

  • pr — analogous GitHub creation workflow
  • compilation — provides error context for bug reports

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

commit

Free

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

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.

The English summary is being prepared. Showing the original description.

rsicarelli/fakt67Updated Oct 23, 2026

See all skills by rsicarelli

Report a problem with this skill