prd
79建立產品需求文件
團隊在啟動功能時,常常只有模糊的目標且缺少需求。此技能會將產品想法轉化為結構化的 PRD,並包含可衡量的標準與技術脈絡。
Manage Stacked GitHub Pull Requests
Large changes become difficult to review when unrelated concerns share one branch. This skill guides dependency-based branch planning and non-interactive stacked PR workflows.
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "gh-stack" from https://skillstore.io/skills/github-gh-stack.md and its manifest at https://skillstore.io/api/skills/github-gh-stack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
正在使用「gh-stack」。 Plan a stack for a billing feature with schema, API, and interface changes.
預期結果:
正在使用「gh-stack」。 The sync command returned success but reported Sync aborted. What should I check?
預期結果:
正在使用「gh-stack」。 I changed API code while working on the frontend branch.
預期結果:
All 72 static findings are false positives from Markdown formatting, ordinary prose, a documentation link, or safe Git command substitutions. No evidence found of prompt injection, credential theft, or unauthorized exfiltration in the four reviewed files. The documented workflow still installs an external extension, modifies Git state, and publishes or merges changes through GitHub.
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
https://skillstore.io/skills/github-gh-stack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/github-gh-stack?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/github-gh-stack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/github-gh-stack/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/github-gh-stack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>github. (2026). gh-stack security audit report (audit version 1) [Author version 0.2.0]. Skillstore. https://skillstore.io/skills/github-gh-stack/audits/1@techreport{github-github-gh-stack-2026,
author = {github},
title = {gh-stack security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/github-gh-stack/audits/1},
note = {Author version 0.2.0}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gh-stack security audit report (audit version 1)"
version: "0.2.0"
type: report
authors:
- name: "github"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/github-gh-stack/audits/1"
identifiers:
- type: other
value: "skillstore:github-gh-stack:audit:1"
description: "Skillstore immutable audit report identifier"
Plan schema, API, and interface branches in dependency order, then submit a linked set of draft pull requests.
Find the branch that owns a change, commit there, and rebase dependent branches while respecting worktree ownership.
Use explicit targets, structured output, remote selection, and documented recovery paths to maintain stacks without interactive menus.
Inspect my current gh-stack state. Summarize branch order, pull request status, and rebase needs without changing branches or publishing anything.
Plan a stack for [feature]. Propose dependency-ordered branches using repository naming conventions. Explain each review scope and wait for approval before creating branches.
Place [change] in its owning branch. Inspect ownership and worktree state, propose targeted staging and upstack rebasing, and request approval before remote updates.
Diagnose divergence between my local and GitHub stacks. Compare both chains, explain recovery options, and preserve branches. Await approval before regrouping or publishing.
作者
github授權
MIT
作者版本
v0.2.0
Skillstore 修訂
r1
儲存庫
https://github.com/github/gh-stack/tree/d4ab7ab47e5b3e3708a27c8c42abcdf4bc321419/skills/gh-stack引用
5fa1d077e6c44bb8da33885064d2b6c190282c6e
維護新鮮度
2026/10/6
使用量
10 次下載 · 0 次瀏覽
檔案結構
建立產品需求文件
團隊在啟動功能時,常常只有模糊的目標且缺少需求。此技能會將產品想法轉化為結構化的 PRD,並包含可衡量的標準與技術脈絡。
打造更好的 Spring Boot 應用程式
Spring Boot 專案可能在分層、設定、測試與安全性方面變得不一致。此技能提供精簡的最佳實務指引,協助使用 Spring Boot 設計可維護的 Java 服務。
安全地重構程式碼
當結構、命名與職責逐漸偏移時,大型程式碼庫會變得難以修改。此技能會引導安全的重構步驟,在改善可維護性的同時保留既有行為。
建立清晰的 Conventional Git 提交
不清楚的提交會使審查與發布歷史更難理解。此技能會分析儲存庫變更、暫存選取的檔案,並建立 Conventional Commit 訊息。
建立 Diataxis 軟體文件
團隊經常需要符合使用者意圖的文件,涵蓋教學、操作指南、參考頁面和解釋。此技能會引導 Claude、Codex 和 Claude Code 釐清範圍、提出大綱,並起草結構化 Markdown。
Create Lean Multi-Stage Dockerfiles
Container images can retain unnecessary build tools and rebuild dependencies too often. This skill guides Dockerfile design with separate build stages, efficient caching, and minimal runtime dependencies.
精通進階 Git 工作流程
由 AutumnsGrove
複雜的 Git 歷史可能很難在不遺失工作的情況下修復。此技能提供 rebase、衝突、bisect、復原和分支管理的引導式工作流程。
更快速審查 GitHub Pull Request
由 Bind
程式碼審查協調通常需要反覆執行 GitHub CLI 檢查與留言。此技能記錄用於分流、指南查找與行內回饋的 PR 審查輔助工具。
Review Defects and Verify Root-Cause Repairs
由 aakashh242
Reviews can miss failure conditions or accept fixes without reliable evidence. Gauntlet guides scoped adversarial reviews, authorized repairs, and revision-bound verification within a finite budget.
建立一致的 GitHub Issue
由 C0ntr0lledCha0s
當 Issue 標題、標籤和專案中繼資料在不同儲存庫之間不一致時,團隊會浪費時間。此技能會引導 Claude、Codex 和 Claude Code 以一致方式建立 GitHub Issue。
Audit NestJS Code with Evidence-Backed Findings
由 amirtaherkhani
NestJS repositories can hide boundary flaws and runtime risks that lint results alone cannot reveal. This skill combines local evidence collection and semantic review into one prioritized report.
使用結構化品質檢查審查程式碼
由 alirezarezvani
程式碼審查可能會遺漏品質、安全性與可維護性問題。此技能會透過腳本、檢查清單與報告產生流程,引導進行結構化審查。