← 返回
未分类 中文

GithubIssue

Generate structured GitHub issue cards for the WeBuddhist team. Use this when a backend dev needs to document a new or changed endpoint, or when a frontend/a...
为 WeBuddhist 团队生成结构化的 GitHub Issue 卡片。当后端开发需要记录新接口或已更改的接口时,或前端需要时使用。
tech-lo
未分类 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 434
下载
💾 0
安装
1
版本
#latest

概述

Context:

The WeBuddhist team (backend, frontend, app devs) uses GitHub issue cards to document API endpoints during integration. Cards must be consistent so any dev can scan them and know: what's the endpoint, what goes in, what comes out, and what can go wrong. This skill generates those cards.

Accepted Inputs:

  • OpenAPI/Swagger spec (YAML/JSON) → extract endpoints automatically
  • Natural language → "we added a language filter to GET /plans/tags"
  • Inline details → method, path, params, response pasted in chat
  • Existing issue number → reads via gh issue view for context
  • Any combination of the above

Instructions:

  1. Parse the input. Extract: HTTP method, path, query params, request body, response body, status codes, headers. If info is missing, mark as [TBD].
  1. Pick the card type:
    • New endpoint → full card
    • Endpoint edit → full card + "Current Behavior" / "Proposed Change" sections after Context
    • Backend fix → full card, focus Context on the bug, still include the related endpoint and response so devs know which API surface is affected
  1. Generate the card using the template below. Do NOT output any conversational text — output ONLY the formatted markdown so it can be directly copied into GitHub.
  1. Show the card to the user for review. Wait for approval before proceeding.
  1. After approval, ask for target repo:
    • Run: gh repo list --limit 50 --json name,description
    • Show list, user picks
  1. Ask for project board:
    • First check auth scope: gh auth status — if project scope is missing, tell user to run gh auth refresh -s project
    • Run: gh project list --owner --format json
    • Show list, user picks
  1. Create and link:
    • gh issue create --repo / --title "" --body "<body>"</code></li><li><code>gh project item-add <project-number> --owner <org> --url <issue-url></code></li><li>Show the issue URL</li></ul></ol><p>Never auto-create. Always: generate → review → repo → board → create.</p><p><strong>Card Template:</strong></p><pre><code># <Short clear title> ## Context <1-2 sentences: why this endpoint exists, or what's changing and why> ## Endpoint \`\`\` <METHOD> <path> \`\`\` ## Headers | Header | Required | Description | |--------|----------|-------------| | `Authorization` | Yes | Bearer token | ## Query Parameters | Parameter | Type | Required | Description | |-----------|------|----------|-------------| ## Request Body \`\`\`json {} \`\`\` ## Response **200 OK** \`\`\`json {} \`\`\` ## Status Codes | Code | Description | |------|-------------| | 200 | Success | | 401 | Unauthorized | | 404 | Not found | | 422 | Validation error | ## Notes - <Edge cases, gotchas, related issues> </code></pre><p>Omit sections that don't apply (e.g., no Request Body for GET, no Query Params for POST with body only).</p><p>For <strong>endpoint edits</strong>, add after Context:</p><pre><code>## Current Behavior ## Proposed Change </code></pre><p><strong>Prerequisites:</strong></p><ul><li>The <code>gh</code> token needs the <code>project</code> scope. If project commands fail, run: <code>gh auth refresh -s project</code></li></ul><p><strong>Rules:</strong></p><ul><li>Realistic example values — Tibetan text for <code>bo</code> fields (<code>སྒོམ</code>), UUIDs for IDs, real names like "Morning Meditation"</li><li>Multilingual fields as objects: <code>{ "en": "Meditation", "bo": "སྒོམ" }</code></li><li>OpenAPI schemas → concrete JSON examples, not raw schema</li><li>Short scannable notes — bullets, not paragraphs</li><li><code>[TBD]</code> for unknowns, never invent behavior</li><li>Always ask user to pick repo and project board</li></ul></div> </div> </div> <div id="tab-versions" class="detail-content"> <div class="detail-section"> <h2>版本历史</h2> <p style="margin-bottom:12px;font-size:14px;color:#94a3b8;">共 1 个版本</p> <ul class="version-list"> <li> <div> <span class="version-tag">v1.0.0</span> <span style="font-size:11px;color:#5b6abf;margin-left:8px;background:#eef0ff;padding:1px 8px;border-radius:10px;">当前</span> </div> <div style="font-size:12px;color:#94a3b8;"> 2026-05-02 11:27 安全 安全 </div> </li> </ul> </div> </div> <div id="tab-security" class="detail-content"> <div class="detail-section"> <h2>安全检测</h2> <div class="sec-grid"> <div class="sec-card"> <h4>腾讯云安全 (Keen)</h4> <div class="sec-status sec-safe"> 安全,无风险 </div> <a href="https://tix.qq.com/search/skill?keyword=dd83e30255ea3cea614572593326740c" target="_blank">查看报告</a> </div> <div class="sec-card"> <h4>腾讯云安全 (Sanbu)</h4> <div class="sec-status sec-safe"> 安全,无风险 </div> <a href="https://static.cloudsec.tencent.com/html-report-v2/2026/05/26/426513_0a645757f61826de23308cc187cfcea6.html?q-sign-algorithm=sha1&q-ak=AKID8JMG1bzBC1dz96qNhssfFftujT1NCoFi&q-sign-time=1781235900%3B1812771900&q-key-time=1781235900%3B1812771900&q-header-list=host&q-url-param-list=&q-signature=b1956f405ccc9d8910ebfafc33845bb5ce1cf8d5" target="_blank">查看报告</a> </div> </div> </div> </div> <!-- Recommended Skills --> <div style="margin-top:24px;"> <h2 style="font-size:18px;font-weight:600;margin-bottom:16px;">🔗 相关推荐</h2> <div class="rec-grid"> <div class="rec-card"> <span class="badge-cat" style="margin-bottom:8px;display:inline-block;">security-compliance</span> <h3><a href="/s/skill-vetter">Skill Vetter</a></h3> <div class="rec-owner">spclaudehome</div> <div class="rec-desc">AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。</div> <div class="rec-stats"> <span style="color:#f39c12;">★ 1,210</span> <span style="color:#5b6abf;">📥 266,122</span> </div> </div> <div class="rec-card"> <span class="badge-cat" style="margin-bottom:8px;display:inline-block;">ai-intelligence</span> <h3><a href="/s/self-improving">Self-Improving + Proactive Agent</a></h3> <div class="rec-owner">ivangdavila</div> <div class="rec-desc">自我反思+自我批评+自我学习+自组织记忆。智能体评估自身工作、发现错误并持续改进。</div> <div class="rec-stats"> <span style="color:#f39c12;">★ 1,349</span> <span style="color:#5b6abf;">📥 317,674</span> </div> </div> <div class="rec-card"> <span class="badge-cat" style="margin-bottom:8px;display:inline-block;">ai-intelligence</span> <h3><a href="/s/self-improving-agent">self-improving agent</a></h3> <div class="rec-owner">pskoett</div> <div class="rec-desc">捕获经验教训、错误和纠正,以实现持续改进。使用时机:(1)命令或操作意外失败;(2)用户纠正……</div> <div class="rec-stats"> <span style="color:#f39c12;">★ 4,055</span> <span style="color:#5b6abf;">📥 795,652</span> </div> </div> </div> </div> </div> <script> document.addEventListener('DOMContentLoaded',function(){ document.querySelectorAll('.detail-tab').forEach(function(btn){ btn.addEventListener('click',function(e){ var tab = this.getAttribute('data-tab'); document.querySelectorAll('.detail-tab').forEach(function(b){b.classList.remove('active')}); document.querySelectorAll('.detail-content').forEach(function(c){c.classList.remove('active')}); this.classList.add('active'); var el = document.getElementById('tab-'+tab); if(el) el.classList.add('active'); }); }); }); </script> <div class="footer"> <p>Skill工具集 © 2026</p> </div></body> </html>