Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

sync-tasks

Estrelas121

Forks28

Atualizado6 de março de 2026 às 10:31

Cerate or Update a GitHub Issue for each Task in the task document.

Instalação

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ê.

Executar no Manus

Fonte

alibaba

alibaba/neug

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	sync-tasks
description	Cerate or Update a GitHub Issue for each Task in the task document.
disable-model-invocation	true

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

Task Confirmation:
- User must explicitly provides the Task ID.
- The format is <FeatureID>-<TaskID>, e.g., F001-T101.
- Confirm Feature and Module. The Feature ID is given above. The Module ID is the first digit of the Task ID, e.g., F001-T101 -> Feature 001, Module 1.
- Locate the task file, i.e., ./specs/<FeatureID>-<FeatureName>/tasks/module_i.md.
- Extract the GitHub Feature Issue from the tasks/metadata.md file.
- Note a submission might relates to multiple tasks.
Check Current Modules:
- View the feature issue and its sub-issues to locate the module issue that related to the task.
- If the module issue is not existing, STOP and ask users to create modules first by /sync-modules.
Create Task Issue:
- For each task required by users, create a new issue on the GitHub.
- The issue title is the task title in the module_i.md file, e.g., [Fxxx-Txxx] <task-title>.
- The body is all content in the task region including description and details.
- Assignee, Label, Project are listed in the initial of the module_i.md file. Do NOT set Milestone.
Update GitHub Information:
- If a new task is created or the content is modified, update the feature issue and module issue on the GitHub.
Link Sub-issue (Use GitHub Sub-issue api):
- Set created Task Issue as the sub-issue of the Module Issue.
- First find the issueId.
- Then link the sub-issue using the following commands:
```
gh api graphql -f query='mutation { addSubIssue(input: {issueId: "xxx", subIssueId: "xxx"}) { issue { id title } subIssue { id title } } }'
```

Mais deste repositório

mesmo repositório

codegraph

alibaba/neug

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

2026-05-18121

create-issue

alibaba/neug

Submit a new issue to the project.

2026-03-06121

create-pr

alibaba/neug

Submit a new Pull Request to the project.

2026-03-06121

generate-testcase

alibaba/neug

Analyze new commits and generate related test cases.

2026-03-06121

speckitplan

alibaba/neug

Execute the implementation planning workflow using the plan template to generate design artifacts.

2026-03-06121

speckitspecify

alibaba/neug

Create or update the feature specification from a natural language feature description.

2026-03-06121

name	sync-tasks
description	Cerate or Update a GitHub Issue for each Task in the task document.
disable-model-invocation	true

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

Task Confirmation:
- User must explicitly provides the Task ID.
- The format is <FeatureID>-<TaskID>, e.g., F001-T101.
- Confirm Feature and Module. The Feature ID is given above. The Module ID is the first digit of the Task ID, e.g., F001-T101 -> Feature 001, Module 1.
- Locate the task file, i.e., ./specs/<FeatureID>-<FeatureName>/tasks/module_i.md.
- Extract the GitHub Feature Issue from the tasks/metadata.md file.
- Note a submission might relates to multiple tasks.
Check Current Modules:
- View the feature issue and its sub-issues to locate the module issue that related to the task.
- If the module issue is not existing, STOP and ask users to create modules first by /sync-modules.
Create Task Issue:
- For each task required by users, create a new issue on the GitHub.
- The issue title is the task title in the module_i.md file, e.g., [Fxxx-Txxx] <task-title>.
- The body is all content in the task region including description and details.
- Assignee, Label, Project are listed in the initial of the module_i.md file. Do NOT set Milestone.
Update GitHub Information:
- If a new task is created or the content is modified, update the feature issue and module issue on the GitHub.
Link Sub-issue (Use GitHub Sub-issue api):
- Set created Task Issue as the sub-issue of the Module Issue.
- First find the issueId.
- Then link the sub-issue using the following commands:
```
gh api graphql -f query='mutation { addSubIssue(input: {issueId: "xxx", subIssueId: "xxx"}) { issue { id title } subIssue { id title } } }'
```