Skip to content
cccskills
FreePublished on GitHub

sync-tasks

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

The English summary is being prepared. Showing the original description.

Works withGitHub
See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

User Input

$ARGUMENTS

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

Outline

  1. 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.
  2. 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.
  3. 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.
  4. Update GitHub Information:

    • If a new task is created or the content is modified, update the feature issue and module issue on the GitHub.
  5. 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 } } }'
      

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

Submit a new issue to the project.

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

Submit a new Pull Request to the project.

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

Analyze new commits and generate related test cases.

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

Vulnerability audit and dataflow analysis built on the neug CPG engine. file_audit (default, recommended): first builds a function-level summary graph (tier1) over the entire project, then incrementally builds detailed CPGs (tier2) on demand for chosen functions; both tiers coexist in a single neug database (unified schema, cross-layer refines edges; C/Java/Python/Rust). All capabilities are exposed as CLI tool subcommands (audit/overview/build/query/methods/paths), so an agent can drive the audit step by step via shell; the audit subcommand can also run the built-in LLM loop. The same tooling also supports a dataflow analysis mode (Workflow C): no vulnerability hunting, only variable-level dataflow tracing for functions of interest, producing dataflow_analysis.json. repo_audit: multi-round LLM/Cypher audit over a full-repo CPG. Use when the user asks to audit a codebase/project for vulnerabilities, scan a project with CPG/neug, run repo_audit/file_audit, find source-to-sink taint paths, or analyze dataflow inside a function. Supports C, Java, Python, and Rust.

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

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

The English summary is being prepared. Showing the original description.

alibaba/neug171Updated Oct 22, 2026

See all skills by alibaba

Report a problem with this skill