원클릭으로 Manus에서 모든 스킬 실행

issue

스타7

포크0

업데이트2026년 7월 23일 01:31

Turn an idea into a well-formed GitHub issue with context, scope and acceptance criteria, correct labels, milestone and board placement. Use when the user types /issue <idea> or asks to create or file an issue.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

milocaetano

milocaetano/quantick

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create a well-formed issue

Steps

Vague-idea check: if there is no concrete deliverable yet, suggest opening a GitHub Discussion instead and stop. Issues are actionable work items only.
Gather — ask at most 2–3 questions, and only for what cannot be inferred:
- Context — what problem this solves, why it matters
- Scope — what is in, and what is explicitly out
- Acceptance criteria — checkboxes answering "how do we know it's done"
Title: type(area): imperative description, matching existing issues (e.g. feat(engine): tick bars (close after N trades)). Everything in English.
Create with gh issue create --body-file - using body sections ## Context, ## Scope, ## Acceptance criteria. Apply one area:* label plus one type:* label (or bug), and the current milestone (v0.1 - Engine core) unless told otherwise.

Add to the board in Todo:

ITEM=$(gh project item-add 1 --owner milocaetano --url <issue-url> --format json --jq '.id')
gh project item-edit --id "$ITEM" --project-id PVT_kwHOA0fkv84BeK9c \
  --field-id PVTSSF_lAHOA0fkv84BeK9czhYnKUg --single-select-option-id f75ad846

Report the issue number and URL.

Label reference

Areas: area:engine, area:feed, area:app
Types: type:feat, type:fix, type:docs, type:test, type:ci, bug

이 저장소의 다른 Skills

같은 저장소

new-task

milocaetano/quantick

Start work on a GitHub issue the right way - read it, branch from updated main with the correct prefix, move the board card to In Progress. Use when the user types /new-task <issue-number> or asks to start or pick up an issue.

2026-07-267

ship

milocaetano/quantick

Deliver the current branch - run the full verification loop, commit, push, open a PR with Closes

2026-07-267

arch-review

milocaetano/quantick

Architecture-first code review for quantick — checks that a change docks as a module, declares its performance impact, proves itself with tests, and hides nothing behind a magic number. Use when the user types /arch-review, asks for a code review, or asks whether a change is modular, extensible or fast enough.

2026-07-257

name	issue
description	Turn an idea into a well-formed GitHub issue with context, scope and acceptance criteria, correct labels, milestone and board placement. Use when the user types /issue <idea> or asks to create or file an issue.

Create a well-formed issue

Steps

Vague-idea check: if there is no concrete deliverable yet, suggest opening a GitHub Discussion instead and stop. Issues are actionable work items only.
Gather — ask at most 2–3 questions, and only for what cannot be inferred:
- Context — what problem this solves, why it matters
- Scope — what is in, and what is explicitly out
- Acceptance criteria — checkboxes answering "how do we know it's done"
Title: type(area): imperative description, matching existing issues (e.g. feat(engine): tick bars (close after N trades)). Everything in English.
Create with gh issue create --body-file - using body sections ## Context, ## Scope, ## Acceptance criteria. Apply one area:* label plus one type:* label (or bug), and the current milestone (v0.1 - Engine core) unless told otherwise.

Add to the board in Todo:

ITEM=$(gh project item-add 1 --owner milocaetano --url <issue-url> --format json --jq '.id')
gh project item-edit --id "$ITEM" --project-id PVT_kwHOA0fkv84BeK9c \
  --field-id PVTSSF_lAHOA0fkv84BeK9czhYnKUg --single-select-option-id f75ad846

Report the issue number and URL.

Label reference

Areas: area:engine, area:feed, area:app
Types: type:feat, type:fix, type:docs, type:test, type:ci, bug