본문으로 건너뛰기
cccskills
무료GitHub에 공개

create-issue

Submit a new issue to the project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구GitHub
설치 방법 보기

포함된 파일(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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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/neug1702026년 10월 19일 업데이트

create-pr

무료

Submit a new Pull Request to the project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/neug1702026년 10월 19일 업데이트

Analyze new commits and generate related test cases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/neug1702026년 10월 19일 업데이트

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/neug1702026년 10월 19일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/neug1702026년 10월 19일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

alibaba/neug1702026년 10월 19일 업데이트

alibaba의 스킬 모두 보기

이 스킬의 문제 신고