thun-res/vlink / .agents/skills/discussion
discussion
Verified调查 VLink 的用法问题、设计取舍、改进想法、经验分享或投票主题,检索 现有 GitHub Discussions 和相关 Issue 去重,用自然、聚焦、证据诚实的 简体中文草拟或发布 Discussion,并可读取完整讨论上下文后草拟或发布 单条顶层评论或楼中楼回复.用户要求"发 discussion"、"开讨论"、 "回复 discussion"、"评论 discussion"或"回应这条讨论"时使用;不得 伪装人类身份、批量回复、制造虚假互动或灌水。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| agents/openai.yaml | config | 225 B |
| references/GITHUB-OPERATIONS.md | markdown | 3.5 KB |
references/GITHUB-OPERATIONS.md
View on GitHub# Discussion GitHub 操作
只执行当前任务需要的命令。任何写入仍须满足主 `SKILL.md` 的单次授权
边界。
## 搜索与分类
确认 GitHub 登录和仓库,查询分类及最近的 Discussion:
```bash
gh auth status
gh repo view --json nameWithOwner
gh api graphql -f query='
query {
repository(owner: "thun-res", name: "vlink") {
id
discussionCategories(first: 50) {
nodes { id name slug description isAnswerable }
}
discussions(first: 100, orderBy: {field: UPDATED_AT, direction: DESC}) {
nodes { number title bodyText url category { name slug } }
pageInfo { hasNextPage endCursor }
}
}
}'
```
存在下一页时用 `after` 游标继续查询,再以主题关键词搜索 open/closed
Issue。
## 读取完整上下文
先由 Discussion 编号取得 `id`,并保留每条评论的 `id` 和 `url`:
```bash
gh api graphql -F number=<编号> -f query='
query($number: Int!) {
repository(owner: "thun-res", name: "vlink") {
discussion(number: $number) {
id number url title body closed category { name isAnswerable }
comments(first: 100) {
nodes {
id url body createdAt author { login }
replies(first: 100) {
nodes {
id url body createdAt author { login }
replyTo { id url }
}
pageInfo { hasNextPage endCursor }
}
}
pageInfo { hasNextPage endCursor }
}
}
}
}'
```
任一连接存在下一页时使用对应 `after` 游标继续读取。
## 创建并回读
正文写入仓库外的 `mktemp` 临时文件。从查询结果取得 repository ID 和
分类 ID 后执行:
```bash
gh api graphql \
-f query='
mutation($repositoryId: ID!, $categoryId: ID!, $title: String!, $body: String!) {
createDiscussion(input: {
repositoryId: $repositoryId,
categoryId: $categoryId,
title: $title,
body: $body
}) {
discussion { number url title category { name } }
}
}' \
-F repositoryId="<repository-id>" \
-F categoryId="<category-id>" \
-f title="<标题>" \
-F body=@"<临时正文文件>"
```
删除临时文件,再按返回编号回读:
```bash
gh api graphql -F number=<编号> -f query='
query($number: Int!) {
repository(owner: "thun-res", name: "vlink") {
discussion(number: $number) {
number url title body category { name } closed
}
}
}'
```
## 发布回复并回读
回复正文写入仓库外的 `mktemp` 临时文件。顶层评论省略 `replyToId`;
回复指定评论时传入已核实的 `replyToId`:
```bash
gh api graphql \
-f query='
mutation(
$discussionId: ID!,
$replyToId: ID,
$body: String!
) {
addDiscussionComment(input: {
discussionId: $discussionId,
replyToId: $replyToId,
body: $body
}) {
comment {
id url body createdAt
author { login }
replyTo { id url }
}
}
}' \
-F discussionId="<discussion-id>" \
-F replyToId="<目标-comment-id>" \
-F body=@"<临时正文文件>"
```
发布顶层评论时不传 `-F replyToId=...`。保存响应中的 comment `id` 和
`url`,删除临时文件,再按返回 ID 回读:
```bash
gh api graphql -F id="<comment-id>" -f query='
query($id: ID!) {
node(id: $id) {
... on DiscussionComment {
id url body createdAt
author { login }
discussion { number url }
replyTo { id url }
}
}
}'
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |