ticket-add — community ticket-add, StarshipBattles, community, ide skills

v1.0.0
GitHub

이 스킬 정보

2D 공간 전투 시뮬레이터에서 효율적인 티켓 관리가 필요한 프로젝트 관리자 에이전트에게 적합합니다. Create new bug or feature tickets (e.g., /ticket-add bug <descriptions> or /ticket-add feature <descriptions>)

ropesend ropesend
[0]
[0]
Updated: 3/15/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
33
Canonical Locale
en
Detected Body Locale
en

2D 공간 전투 시뮬레이터에서 효율적인 티켓 관리가 필요한 프로젝트 관리자 에이전트에게 적합합니다. Create new bug or feature tickets (e.g., /ticket-add bug <descriptions> or /ticket-add feature <descriptions>)

이 스킬을 사용하는 이유

`Tickets/protocols/01_ingest_ticket.md` 프로토콜을 사용하여 티켓摄取와 프로토콜 구성의 단순화를 통해 에이전트에 권한을 부여합니다. 버그 및 기능 티켓 유형을 지원하며 PREFIX 및 ACTIVE_DIR 설정을 사용자 지정할 수 있습니다.

최적의 용도

2D 공간 전투 시뮬레이터에서 효율적인 티켓 관리가 필요한 프로젝트 관리자 에이전트에게 적합합니다.

↓ 실행 가능한 사용 사례 for ticket-add

2D 공간 전투 시뮬레이터 프로젝트의 티켓 데이터 입력 자동화
버그 및 기능 티켓의 프로토콜 구성
2D 공간 전투 시뮬레이터 환경에서 티켓 관리

! 보안 및 제한 사항

  • `Tickets/protocols/01_ingest_ticket.md` 프로토콜을 따라야 함
  • 2D 공간 전투 시뮬레이터 프로젝트만 해당
  • 코딩 능력 없음, 데이터 입력만 가능

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is ticket-add?

2D 공간 전투 시뮬레이터에서 효율적인 티켓 관리가 필요한 프로젝트 관리자 에이전트에게 적합합니다. Create new bug or feature tickets (e.g., /ticket-add bug <descriptions> or /ticket-add feature <descriptions>)

How do I install ticket-add?

Run the command: npx killer-skills add ropesend/StarshipBattles/ticket-add. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for ticket-add?

Key use cases include: 2D 공간 전투 시뮬레이터 프로젝트의 티켓 데이터 입력 자동화, 버그 및 기능 티켓의 프로토콜 구성, 2D 공간 전투 시뮬레이터 환경에서 티켓 관리.

Which IDEs are compatible with ticket-add?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for ticket-add?

`Tickets/protocols/01_ingest_ticket.md` 프로토콜을 따라야 함. 2D 공간 전투 시뮬레이터 프로젝트만 해당. 코딩 능력 없음, 데이터 입력만 가능.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ropesend/StarshipBattles/ticket-add. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use ticket-add immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

ticket-add

Install ticket-add, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Add Ticket

Protocol: Tickets/protocols/01_ingest_ticket.md

Read and follow the full protocol file.

Your Role

Adopt the Project Manager persona. No coding — data entry only.

Arguments

Parse the first word of $ARGUMENTS as the ticket type. Everything after is the ticket description(s).

Input: $ARGUMENTS

Configuration

Set these values based on ticket type:

BugFeature
PREFIXBUGFEAT
ACTIVE_DIRDebugging/active_bugsFeatures/active_features
DASHBOARDDebugging/debug_plan.mdFeatures/feature_plan.md

Execution

  1. READ the DASHBOARD to identify the next sequential {PREFIX}-XX ID.
  2. PARSE the descriptions into separate tickets.
  3. CREATE ticket files in {ACTIVE_DIR}/{PREFIX}-XX.md for each ticket:
    • Paste the exact, raw description into the file
    • Initialize sections: ## Description, ## Priority, ## Status (Pending), ## Work Log
    • Set Priority:
      • Bugs: Critical (crashes/blocks), High (feature broken), Medium (minor/visual), Low (polish)
      • Features: Critical (required for release), High (significant impact), Medium (nice-to-have), Low (minor enhancement)
  4. UPDATE DASHBOARD with new entries.
  5. REPORT the IDs created and exit.

CONSTRAINT: DO NOT start analysis or write any code. Just perform the data entry.

관련 스킬

Looking for an alternative to ticket-add or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

★ 149.6k
⑂ 0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

★ 138.4k
⑂ 0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

★ 98.6k
⑂ 0
개발자