show-github-search-result
Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 2.6k
- Forks
- 817
01 前言 Front Matter
- name
- show-github-search-result
- description
- Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.
- user-invokable
- false
03 SKILL.md 正文
Render GitHub Search Result
Purpose
To take the results of a GitHub search query, which may include issues or pull requests, and render them in a human-friendly markdown table format. This skill extracts the relevant information from each search result and organizes it in a way that is easy to read and understand, allowing users to quickly grasp the key details of each issue or pull request without having to parse through raw data.
Usage
To use this skill, pass raw search results from a GitHub search query. The skill will then process the data and generate a markdown table that summarizes the key information for each issue or pull request, such as the title, author, labels, state, and any other relevant details. This makes it easier for users to review and analyze the search results at a glance.
How to Render GitHub Search Results
- If you have the original query, use that to help determine the most important fields to include in the table. Ex:
- If the query included a specific label, make sure to not include that label in the table as all results will have it.
- If the query included "is:pr", then focus on fields relevant to pull requests such as "review status" and "merge status".
- Include a column related to the sort value, if given.
- Don't include columns that will all have the same value for all the resulting issues.
- Always include a column for the number and title of the item. Format the number as a markdown link to the issue or PR. Ex: #123
04 同仓库更多 Skills
summarize-github-issue-pr-notification
Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.
suggest-fix-issue
Given the details of an issue, suggests a fix for the issue.
form-github-search-query
Forms a GitHub search query based on a natural language query and the type of search (issue or PR). This skill helps users create effective search queries to find relevant issues or pull requests on GitHub.
create-pull-request
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.
address-pr-comments
Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.
write-changelog
Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.