操作文档
- 作者仓库星标 54
- 许可证 MIT
- 作者仓库 skills
- 领域
- 效率工具
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @xixu-me · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 需要 · GitHub
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
GitHub Actions questions are easy to answer from stale memory. Use this skill to ground answers in official GitHub documentation and return the closest authoritative page instead of generic CI/CD advice.
## When to Use
Use this skill when the request is about:
- GitHub Actions concepts, terminology, or product boundaries
- Workflow YAML, triggers, jobs, matrices, concurrency, variables, contexts, or expressions
- GitHub-hosted runners, larger runners, self-hosted runners, or Actions Runner Controller
- Artifacts, caches, reusable workflows, workflow templates, or custom actions
- Secrets, `GITHUB_TOKEN`, OpenID Connect, artifact attestations, or secure workflow patterns
- Environments, deployment protection rules, deployment history, or deployment examples
- Migrating from Jenkins, CircleCI, GitLab CI/CD, Travis CI, Azure Pipelines, or other CI systems
- Troubleshooting workflow behavior when the user needs documentation, syntax guidance, or official references
Do not use this skill for:
- A specific failing PR check, missing workflow log, or CI failure triage. Use `gh-fix-ci`.
- General GitHub pull request, branch, or repository operations. Use `github`.
- CodeQL-specific configuration or code scanning guidance. Use `codeql`.
- Dependabot configuration, grouping, or dependency update strategy. Use `dependabot`.
## Workflow
### 1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started or tutorials
- Workflow authoring and syntax
- Runners and execution environment
- Security and supply chain
- Deployments and environments
- Custom actions and publishing
- Monitoring, logs, and troubleshooting
- Migration
If you need a quick starting point, load `references/topic-map.md` and jump to the closest section.
### 2. Search official GitHub docs first
- Treat `docs.github.com` as the source of truth.
- Prefer pages under <https://docs.github.com/en/actions>.
- Search with the user's exact terms plus a focused Actions phrase such as `workflow syntax`, `OIDC`, `reusable workflows`, or `self-hosted runners`.
- When multiple pages are plausible, compare 2-3 candidate pages and pick the one that most directly answers the user's question.
### 3. Open the best page before answering
- Read the most relevant page, and the exact section when practical.
- Use the topic map only to narrow the search space or surface likely starting pages.
- If a page appears renamed, moved, or incomplete, say that explicitly and return the nearest authoritative pages instead of guessing.
### 4. Answer with docs-grounded guidance
- Start with a direct answer in plain language.
- Include exact GitHub docs links, not just the docs homepage.
- Only provide YAML or step-by-step examples when the user asks for them or when the docs page makes an example necessary.
- Make any inference explicit. Good phrasing:
- `According to GitHub docs, ...`
- `Inference: this likely means ...`
## Answer Shape
Use a compact structure unless the user asks for depth:
1. Direct answer
2. Relevant docs
3. Example YAML or steps, only if needed
4. Explicit inference callout, only if you had to connect multiple docs pages
Keep citations close to the claim they support.
## Search and Routing Tips
- For concept questions, prefer overview or concept pages before deep reference pages.
- For syntax questions, prefer workflow syntax, events, contexts, variables, or expressions reference pages.
- For security questions, prefer `Secure use`, `Secrets`, `GITHUB_TOKEN`, `OpenID Connect`, and artifact attestation docs.
- For deployment questions, prefer environments and deployment protection docs before cloud-specific examples.
- For migration questions, prefer the migration hub page first, then a platform-specific migration guide.
- If the user asks for a beginner walkthrough, start with a tutorial or quickstart instead of a raw reference page.
## Common Mistakes
- Answering from memory without verifying the current docs
- Linking the GitHub Actions docs landing page when a narrower page exists
- Mixing up reusable workflows and composite actions
- Suggesting long-lived cloud credentials when OIDC is the better documented path
- Treating repo-specific CI debugging as a documentation question when it should be handed to `gh-fix-ci`
- Letting adjacent domains absorb the request when `codeql` or `dependabot` is the sharper fit
## Bundled Reference
Read `references/topic-map.md` only as a compact index of likely doc entry points. It is intentionally incomplete and should never replace the live GitHub docs as the final authority.
章节与文件索引
按说明文件中的顺序排列。
何时使用
1. 对请求进行分类
2.先搜索GitHub官方文档
3.回答前先打开最佳页面
4. 使用基于文档的指导进行回答
文件/命令 -> GITHUB_TOKEN · gh-fix-ci · codeql · dependabot · references/topic-map.md · docs.github.com · workflow syntax · OIDC
内容校验值 -> 454f564ed55c
当前原文的自动摘译,尚未人工审校。
何时使用
当请求涉及以下内容时,请使用此技能: GitHub Actions 概念、术语或产品边界 工作流 YAML、触发器、作业、矩阵、并发、变量、上下文或表达式 GitHub 托管的运行器、大型运行器、自托管运行器或 Actions Runner 控制器工件、缓存、可重用工作流、工作流模板或自定义操作
1. 对请求进行分类
在搜索之前确定问题属于哪个存储桶: 入门或教程 工作流创作和语法 运行器和执行环境 安全和供应链
2.先搜索GitHub官方文档
将
docs.github.com视为事实来源。首选 https://docs.github.com/en/actions 下的页面。使用用户的确切术语以及重点操作短语进行搜索,例如workflow syntax、OIDC、reusable workflows或self-hosted runners。当多个页面都可行时,比较 2-3 个候选页面并选择最能直接回答用户问题的页面。3.回答前先打开最佳页面
阅读最相关的页面,并在实际情况下阅读确切的部分。仅使用主题图来缩小搜索空间或显示可能的起始页面。如果页面出现重命名、移动或不完整,请明确说明并返回最近的权威页面,而不是猜测。
4. 使用基于文档的指导进行回答
首先用简单的语言直接回答。包含确切的 GitHub 文档链接,而不仅仅是文档主页。仅当用户要求或文档页面需要示例时才提供 YAML 或分步示例。明确任何推论。好的措辞:
According to GitHub docs, ...