inbox-add-reaction
Add a reaction to a GitHub issue or pull request
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 66
- Forks
- 12
01 前言 Front Matter
- name
- inbox-add-reaction
- tools
- [ "execute" ]
- description
- Add a reaction to a GitHub issue or pull request
03 SKILL.md 正文
Add Reaction
Add an emoji reaction to an issue or pull request.
Command
gh api --method POST /repos/{owner}/{repo}/issues/{number}/reactions -f content={reaction}
Available reactions
+1(thumbs up ?)-1(thumbs down ?)laugh(?)confused(?)heart(❤️)hooray(?)rocket(?)eyes(?)
Replace {owner}, {repo}, {number}, and {reaction} with the appropriate values. Note: this endpoint works for both issues and pull requests (PRs are issues in GitHub's API).
04 同仓库更多 Skills
generate-test-video
Make a short narrated "how to test" or "how to verify" video for a VS Code test plan item (TPI), a fixed bug, or a few fixed bugs of one area: recorded in real VS Code Insiders in a throwaway profile, every step checked in the app, with captions, a zoom, flags that pause where something is wrong, a verdict slide and a recap. macOS. USE FOR: "make a how-to-test video for TPI 342400", "a video to verify issue 341013", "how-to-verify video for bugs 339711 339712 339714". DO NOT USE FOR: explaining a PR to someone who won't test it (use pr-studio:generate-video), plain screen recordings, editing an existing video.
session-timeline
Open a live timeline canvas for the current Copilot session. Use when asked to inspect session events, system prompts, reasoning, tool executions, or subagent activity in a session timeline.
review-plan
Review an implementation plan produced by the Plan agent. It is CRITICAL to review plans before handing off to implementation — plans often have gaps, incorrect assumptions, or suboptimal sequencing that are cheaper to catch now than after coding. Use when the user asks to 'review the plan', 'check my plan', 'is this plan ready', or after the Plan agent produces a plan.md.
review-areas
In-depth code review that fans out parallel subagents across review areas — CRITICAL after non-trivial development. USE FOR: "in-depth review of a pull request", "code quality check or bug hunt", "review correctness, tests, security, performance and product areas", "review after any non-trivial development phase". DO NOT USE FOR: "plan a new implementation", "explain how existing code works".
generate-video
Make the shortest narrated video that fully explains a GitHub pull request (at most 90 seconds, captions, diagrams chosen for the PR, and real footage of the app, before and after side by side, when the change is visible) in one white Microsoft look. USE FOR: "/generate-video 12345", "make a video of this PR", "explain PR <url> in a video", "a video for my manager about this PR". DO NOT USE FOR: a screen recording on its own (no PR to explain), editing existing videos, slide decks (use generate-presentation).
generate-presentation
Make the shortest slide deck (a 16:9 PDF with speaker notes, at most 12 slides) that fully explains a GitHub pull request, in one white Microsoft look: one idea per slide, drawn as diagrams, with screenshots of the real app when the change is visible, every fact from the PR. USE FOR: "/generate-presentation 12345", "make slides about this PR", "a deck for my manager on PR <url>", "present this pull request". DO NOT USE FOR: editing PowerPoint files, videos (use generate-video), decks with no pull request behind them.