Skip to content
cccskills
FreePublished on GitHubEnglish overview

Accessing GitHub issues

Use this skill to read GitHub issue details and comments from the command line with `gh`. It covers issues referenced by number or URL, including issues in other repositories, and keeps access read-only so issue state is not changed.

OriginalShow the original description

Instructions for safely viewing and accessing GitHub issues by way of command line.

carbon-language/carbon-lang33,930 stars(GitHub 33,930 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Good for

  • Reading an issue and its full comment history
  • Opening an issue referenced by URL
  • Viewing an issue from another repository
  • Checking issue context without changing its state

Overview

What it does

This skill shows how to view GitHub issues from the command line with gh. You can read an issue by number and include its comments with --comments to get the full context. For issues in another repository, specify the repository with -R or --repo. When given a URL, identify the owner, repository name, and issue number from it. For issues with many comments, the skill also shows how to use JSON output and jq to extract comment bodies.

When it helps

Use this skill when an agent needs to investigate or review an issue from the command line. It is useful for reading the issue body and comments without opening a browser, and for looking up issues in a different repository.

Example requests

  • “Read the body and comments for this issue number.”
  • “Find the issue details from this GitHub URL.”
  • “Show an issue from another repository, including its comments.”

Notes

This skill uses the gh command. It prohibits creating, editing, commenting on, closing, or deleting issues, so issue state remains unchanged.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt limits access to view and list, and forbids creating, editing, commenting, closing, or deleting issues.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt names the gh command but gives no installation or authentication steps.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

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

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Accessing GitHub issues

<!-- Part of the Carbon Language project, under the Apache License v2.0 with LLVM Exceptions. See /LICENSE for license information. SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception -->

This skill provides instructions for AI assistants on how to access and view GitHub issues. Agents should strongly prefer using the command line gh tool to access and view the contents of issues rather than viewing their contents by way of a web browser.

Safety First

[!IMPORTANT] AI assistants MUST NOT modify any GitHub issue state. Only use read-only access commands like view or list. Do NOT comment, edit, create, close, or delete issues.

Accessing Issues

Agents must use this skill to access issues regardless of how they are mentioned (for example, by URL or by issue number).

Basic View

To view an issue in the current default repository (expected to be Carbon):

gh issue view <issue_number>

Including Full Context (All Comments)

To ensure the view includes the entire context of the issue, always include the --comments flag to dump all comments:

gh issue view <issue_number> --comments

[!TIP] If the issue is extremely large and comments are truncated, or you need to process comments programmatically, use the JSON output with jq:

gh issue view <issue_number> --json comments --jq '.comments[].body'

Accessing Issues in Other Repositories

To view an issue in another repository (for example, LLVM), use the -R or --repo flag to specify the repository:

gh issue view <issue_number> -R <owner>/<repo> --comments

Examples:

  • LLVM Issue:

    gh issue view 5678 -R llvm/llvm-project --comments

  • Carbon Issue (Explicit):

    gh issue view 1234 -R carbon-language/carbon-lang --comments

Mentions via URL

If an issue is mentioned via URL, parse the URL to extract the repository owner, repository name, and issue number.

  • URL pattern: https://github.com/<owner>/<repo>/issues/<number>
  • Extraction:
    • Host: github.com
    • Owner: <owner>
    • Repo: <repo>
    • Number: <number>

Run the command specifying the repository:

gh issue view <number> -R <owner>/<repo> --comments

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

Agent tools

FreeSummary

Use this skill to guide an AI assistant working in the Carbon repository on viewing, searching, and editing files with specialized environment tools. It also sets rules for temporary files and when custom programs may be used.

  • Choosing approved tools to view, search, or edit files
  • Checking where temporary analysis and test files belong
  • Deciding when a custom transformation program is allowed
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

Bazel usage

FreeSummary

Follow the Carbon project's Bazel workflow through Bazelisk, a version-managing launcher. Learn commands for building targets, running tests and binaries, enabling AddressSanitizer, and refreshing cached state after system dependency changes.

  • Building a Carbon target
  • Running focused project tests
  • Launching a Bazel-built binary
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

Builtin functions

FreeSummary

Use this skill to implement builtin functions in the Carbon compiler, from registering a function name and checking its signature to evaluating constant calls and generating LLVM IR for runtime calls. It also covers prelude bindings and focused tests.

  • Registering a new Carbon builtin function
  • Adding compile-time evaluation behavior
  • Lowering runtime builtins to LLVM IR
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

Code style

FreeSummary

Apply Carbon toolchain conventions for formatting Bazel, C++, Carbon, Markdown, and Python files. The skill also covers clear comments and documentation, accurate names, design choices, and concise commit descriptions.

  • Formatting a changed source file
  • Writing or revising code comments
  • Choosing names that match their meaning
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

Diagnostics

FreeSummary

Use this skill to add or revise diagnostics in the Carbon toolchain. It explains how to register message kinds, format typed arguments, attach source labels and context, and verify that diagnostics follow the project’s wording and test coverage rules.

  • Adding an error or warning to the Carbon compiler
  • Attaching source locations and explanatory labels
  • Checking diagnostic wording and formatting conventions
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

GitHub CLI usage

FreeSummary

Use `gh`, the GitHub command-line tool, to list, inspect, and search issues, pull requests, repositories, and code. The skill also explains read-only REST and GraphQL queries, pagination, and ways to filter or format returned data.

  • Checking an issue or pull request
  • Searching issues, code, or repositories
  • Querying GitHub data with the API
carbon-language/carbon-lang33.9KUpdated Oct 26, 2026

See all skills by carbon-language

Report a problem with this skill