Skip to content
cccskills
FreePublished on GitHub

update-with-comments

Check comments from the Pull Request on the GitHub and update code.

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

Works withGitHub
See how to install

Files included (1)

  • SKILL.md1.5 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. Locate the Pull Request:

    • If user explicitly provides the PR ID
      • Stash current changes and checkout to the PR branch.
    • If user does not provide the PR ID
      • Search the PR on the current branch
    • If there is multiple PRs or no PR, STOP and report to users.
  2. Get PR comments:

    • Obtain conversation comments: gh pr view <pr-id> --comments.
    • Obtain inline comments: gh api repos/:owner/:repo/pulls/<pr-id>/comments.
    • Analysis all comments and align intention, e.g., Approve, Question, Request Changes, etc.
  3. Update Code:

    • If a comment intention is Approve, skip the update.
    • If a comment intention is Question, you have to explain your understanding based on the code and comments.
    • If a comment intention is Request Changes, e.g., typos, code style, potential bugs, optimization chances, etc.
      • Try to update the code to fix the problem in the workspace.
      • If the update is successfully fixed and pass tests, add a new comments to confirm the update.
      • Otherwise, report the problem and ask users to review the comment.
  4. Report & Submit: Generate a summary to show all comments and their updates. Then, commit the changes and push to the PR branch.

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/neug170Updated Oct 21, 2026

Submit a new issue to the project.

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

alibaba/neug170Updated Oct 21, 2026

Submit a new Pull Request to the project.

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

alibaba/neug170Updated Oct 21, 2026

Analyze new commits and generate related test cases.

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

alibaba/neug170Updated Oct 21, 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/neug170Updated Oct 21, 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/neug170Updated Oct 21, 2026

See all skills by alibaba

Report a problem with this skill