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

create-issue

Submit a new issue to the project.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md2.9 KB
  • scripts/gh-update.sh762 B
  • templates/bug-issue.md750 B
  • templates/feature-issue.md597 B

SKILL.md(原文)

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

User Input

$ARGUMENTS

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

Outline

  1. Determine Issue Type: Check the user input and determine the issue type.

    • Bug Report. Report an existing bug, error, or failure during the execution.
    • Feature Request. Request a new feature or improvement for the project.
  2. Load Template: Load the template in a temporary file.

    • Bug Report Template. Load templates/bug-issue.md.
    • Feature Request Template. Load templates/feature-issue.md.
  3. Anlyze User Input: Analyze the user input and fill the template.

    • Issue Title should be brief, e.g., "Error in executing xxx work/function/file", "Failed to execute xxx".
    • The assignee and labels should be inferred. You can use GitHub CLI commands to get available assignee and label list. @me can be directly used.
    • Then the issue content should be filled with the user input and context.
    • The error message should only contains important information, i.e., traceback and error log. Skip massive logs.
    • For Bug Report, must attach the context, i.e., the error message in the terminal.
    • For Bug Report, provide a minimal reproduction scenario when possible: reduce the failure to the smallest set of commands, queries, or data that still triggers the bug, instead of copying the full original workload. When the repository is available locally, try to actually run the scenario to confirm it reproduces before filing. If a minimal scenario cannot be derived from the available context, state that explicitly in the issue.
  4. User Revision:

    • Open the temporary file and let the user review the issue content.
    • Modify the issue content by the user's feedback until the user is approved.
  5. Submit Issue: Submit the issue to the project.

    • Note the initial lines are issue settings and the remaining part is the real issue content.
    • All issue settings must be set when creating the issue.
    gh issue create \
        --title "<issue-title>" \
        --body "<issue-content>" \
        --label "<label>" \
        --assignee "<assignee>" \
        --project "<project>"
    
    • Using the following command to link the parent issue if required:
    gh api graphql -f query='mutation { addSubIssue(input: {issueId: "xxx", subIssueId: "xxx"}) { issue { id title } subIssue { id title } } }'
    
  6. Delete Temporary File: Delete the temporary file After the issue is created.

Appendix: Update GitHub CLI For Projects The default GitHub CLI is too old and not support the new projects feature. If report Projects (classic) is being deprecated, you need to update the GitHub CLI. The script scripts/gh-update.sh will update the GitHub CLI and refresh authentication for projects.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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-pr

無料

Submit a new Pull Request to the project.

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

alibaba/neug1692026年10月9日 更新

Analyze new commits and generate related test cases.

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

alibaba/neug1692026年10月9日 更新

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日 更新

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

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

alibaba/neug1692026年10月9日 更新

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

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

alibaba/neug1692026年10月9日 更新

alibaba のスキルをすべて見る

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