to-tickets

Break a spec or plan into trackable GitHub issues. Use when a plan/spec needs splitting into work items, or the task mentions "tickets", "工单", "break into issues", "分解任务". Emits one issue per independently completable unit with acceptance criteria.

Ir para a instalação

Repositório: znlgis/my-opencode-deepseek-config
Última atividade na origem: 1 de setembro de 2026 às 03:59
Idioma detectado do SKILL.md: inglês
Estrelas: 57
Forks: 13

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/znlgis/my-opencode-deepseek-config --skill to-tickets

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

code-review

Lightweight single-pass code review for a diff/branch/PR. Use when reviewing changes, checking a PR, or the task mentions "code review", "review my changes", "review this PR", "找 bug", "审查代码". Reports blockers (critical/major) and notes (minor/nit) with evidence; never rewrites code.

2026-09-01

opencode-config

Author and modify OpenCode config in this repository — opencode.json, agents, skills, commands, permissions. Use when editing opencode.json, adding or changing an agent, writing a skill or command, adjusting model routing/permissions, or the task mentions "opencode config", "agent prompt", "SKILL.md", "command", or "permission".

2026-09-01

gh-cli

Patterns for invoking the GitHub CLI (gh v2.98.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets, skills, and gh api fallback.

2026-09-01

Ver todas deste repositório

name	to-tickets
description	Break a spec or plan into trackable GitHub issues. Use when a plan/spec needs splitting into work items, or the task mentions "tickets", "工单", "break into issues", "分解任务". Emits one issue per independently completable unit with acceptance criteria.

To Tickets

Turn a written spec or plan into a set of trackable issues. One issue per unit of work, each verifiable on its own.

When to use

A spec/plan exists and needs to become actionable, reviewable issues — not when the work is a single step you can just do inline.

How to break down

One issue = one unit that can be completed and verified independently.
Every issue carries acceptance criteria (the observable "done" condition).
Keep issues small enough to finish and review in one session; split anything that would outlive one.

Creating issues with `gh`

gh issue create --title "<summary>" --body "<body>" --assignee @me

--body holds the scope, acceptance criteria, and dependency notes.
Use --type Task (or Bug/Feature) when the repo uses issue types.
Batch-create from a plan: one gh issue create per ticket.

Notes

Granularity: aim for units a single agent session can finish — not one giant issue, not twenty trivial ones.
Dependencies: annotate blocking relationships (e.g. "blocked by #12") rather than assuming order.
Don't create issues for work you're about to do inline — tickets are for tracking work across sessions or humans.

to-tickets

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

To Tickets

When to use

How to break down

Creating issues with gh

Notes

Mais deste repositório

To Tickets

When to use

How to break down

Creating issues with gh

Notes

Creating issues with `gh`

Creating issues with `gh`