本文へ移動
cccskills
無料GitHub で公開

sync-modules

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

alibaba/neug
インストール方法を見る

含まれるファイル（1）

  • SKILL.md2.2 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

User Input

$ARGUMENTS

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

Outline

  1. Locate Feature & Tasks:

    • Extract the feature name from the branch name or user input like ###-feature-name, e.g., 001-feature-name.
    • Find the most likely feature in the specs directory, i.e., ./specs/[###-feature-name]. The feature id and name must be exact match.
    • The feature spec must has a task directory (i.e, tasks/) including a metadata.md file and multiple module_i.md files. All paths must be absolute.
    • Find the feature issue link in the tasks/metadata.md file. If not exists, search the feature issue on the GitHub by the prefix [###-feature-name]. The feature id and name must be exact match. If not found, stop and report error "Feature issue not found: [###-feature-name]".

  2. Check Current Modules:

    • View the feature issue and its sub-issues on the GitHub to confirm the current modules.
    • If some modules are missing, go to Step 3 to create them.
    • If some modules are modified (local files and remote issues are different), synchronize them.

  3. Create Module Issue: (For each module_i.md file)

    • Create a new issue on the GitHub.
    • The issue title is [###-feature-name] Module <i>: <description>, e.g., [001-add-frontend] Module 1: Setup for biagent.
    • The body is the Goal (at the beginning of the module_i.md file) and tasks list (at metadata.md) of the module.
    • The Assignee is given in the module_i.md file. @me by default.
    • The Labels are given in the module_i.md file.
    • The Milestone is given in the module_i.md file. Skip if None is given.
    • The Project is given in the module_i.md file. Skip if None is given.

  4. Link Sub-issue (Use GitHub Sub-issue api):

    • Set each Module Issue as the sub-issue of the Feature 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 } } }'

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

codegraph

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

create-issue

無料

Submit a new issue to the project.

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

create-pr

無料

Submit a new Pull Request to the project.

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

generate-testcase

無料

Analyze new commits and generate related test cases.

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

neug-codescope

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

speckit.plan

無料

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

日本語の概要は準備中です。原文の説明を表示しています。

alibaba/neug1692026年10月9日 更新

alibaba のスキルをすべて見る

このスキルの問題を報告する