agentsclimarketplace

Github issue creator

Skill lteawoo/skills/skills/github-issue-creator

A collection of practical AI agent skills for app development and code workflows.

Install
npx -y skills add lteawoo/skills --skill github-issue-creator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Structure bug reports, requirements, logs, or screenshots into actionable GitHub issues. Use it when you need acceptance criteria, scope definition, and a validation plan.

SKILL.md

2.2 KB, as published. Nobody here has run it

GitHub Issue Creator

Purpose

Turn unstructured input into a GitHub issue that is ready for development.

Core Principles

  1. Put the acceptance criteria at the top using Given/When/Then.
  2. Separate In Scope from Out of Scope.
  3. An issue without a validation plan, automated or manual, is not complete.
  4. If information is missing, ask follow-up questions instead of guessing.
  5. Replace sensitive information with placeholders such as [USER_ID] or [TOKEN].
  6. Include at least one recommended PR label for release categorization in the issue body.

Release Label Hints

Based on .github/release.yml, PR labels determine the release category.

  • New Features: feat, feature, enhancement
  • Bug Fixes: fix, bug, bugfix
  • Maintenance (Chore): chore, dependencies, ci, build, refactor
  • Unmatched or missing labels: Other Changes

Recommended:

  1. Include the recommended PR label in the issue.
  2. Apply the same label on the implementation PR to avoid release-note classification gaps.

Output Format

Title

  • [type] one-line summary
  • type: feat|fix|refactor|docs|chore|test

Acceptance Criteria

  • Given ...
  • When ...
  • Then ...

Background or Problem

  • Current state
  • User or operational impact

Scope

  • In Scope
  • Out of Scope

Implementation Direction

  • Target areas or modules
  • Constraints and dependencies
  • Risks
  • Recommended PR label (feat|feature|enhancement|fix|bug|bugfix|chore|dependencies|ci|build|refactor)

Validation Plan

  • Automated validation: lint, build, test
  • Manual validation: key scenarios
  • For UI changes: screenshot checkpoints

Completion Criteria

  • AC satisfied
  • No regressions
  • Release impact and cautions documented

Checklist

  • Implementation complete
  • Tests complete
  • Regression check complete
  • Recommended PR label assigned or confirmed
  • Docs or release notes updated if needed

When Information Is Missing

  • Draft the issue first.
  • Limit follow-up questions to three.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.