issue-md-writer

Create and draft markdown-based issue documents (bug reports, feature plans, RFCs, ADRs, tasks, retrospectives) in the top-level `.issues/` folder. Use this skill whenever you need to document software issues, feature proposals, architectural decisions, work items, or post-mortems. Includes templates, metadata indexing, and structured YAML frontmatter. Different from issue tracker systems — this is for archival, decision-making, and knowledge base documents.

跳到安装

仓库: arisng/github-copilot-fc
最近来源活动: 2026年6月17日 14:09
检测到的 SKILL.md 语言: 英语
星标: 5
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/arisng/github-copilot-fc --skill issue-md-writer

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

10 个文件

SKILL.md

来源说明 · 只读预览

name: issue-md-writer
description: Create and draft markdown-based issue documents (bug reports, feature plans, RFCs, ADRs, tasks, retrospectives) in the top-level `.issues/` folder. Use this skill whenever you need to document software issues, feature proposals, architectural decisions, work items, or post-mortems. Includes templates, metadata indexing, and structured YAML frontmatter. Different from issue tracker systems — this is for archival, decision-making, and knowledge base documents.
metadata: {"version":"2.2.0","author":"arisng"}

# MD Issue Writer ## Overview This skill enables the creation of concise, one-page technical documents for software issues, features, decisions, and work items. Each document follows a standardized YAML frontmatter and markdown structure, making them discoverable and indexable across the knowledge base. ## When to Use Each Document Type Use this decision tree to select the right template: | **Situation** | **Document Type** | **Purpose** | |---|---|---| | Something broke or isn't working | **Bug Report** | Root cause analysis, prevention, lessons learned | | Build/ship a new capability | **Feature Plan** | Goals, requirements, implementation approach, risks | | Need consensus on architectural direction | **RFC** | Proposal, motivation, design, alternatives, Q&A | | Made a major technical decision | **ADR** | Document the decision, context, and consequences | | Have specific work to accomplish | **Task** | Objectives, acceptance criteria, checklist | | Learned something from an incident/project | **Retrospective** | What happened, what went well, lessons, actions | ## Workflow 1. **Choose the document type** using the decision tree above or by reviewing the templates in `templates/`. 2. **Gather required metadata**: title, description, severity (if applicable), status, author (if applicable). 3. **Generate the document** using the provided script or by copying a template into the new `.issues/` directory (it will be created automatically). 4. **Fill in the content** following the template structure. 5. **(Optional) Index all documents** by running the metadata extraction script to keep the central index current. ## Usage Create a new issue document via script: ```bash python scripts/create_issue.py --type "Bug" --title "Fix login timeout" --description "Users are logged out after 5 minutes" --severity "High" ``` Or copy a template directly: ```bash cp templates/<type>.md .issues/<date>_<slug>.md ``` To extract metadata and regenerate the index of all issues: ```bash python scripts/extract_issue_metadata.py ``` ## Template Reference Each issue type has its own reference file in `templates/`: - **bug-report.md** — Incident analysis with root cause, solution, and prevention steps - **feature-plan.md** — Feature proposal with goals, requirements, and implementation approach - **rfc.md** — RFC proposal with motivation, design, alternatives, and open questions - **adr.md** — Architecture decision record for major technical choices - **task.md** — Work item with objectives, acceptance criteria, and references - **retrospective.md** — Post-incident or post-project learning document See `templates/index.md` for a complete overview and quick-reference guide. ## Resources ### scripts/ - `create_issue.py` — Generate issue documents based on templates - `extract_issue_metadata.py` — Extract metadata and regenerate the index ### templates/ - `index.md` — Quick reference and overview of all template types - `bug-report.md`, `feature-plan.md`, `rfc.md`, `adr.md`, `task.md`, `retrospective.md` — Individual templates

在 GitHub 查看

返回搜索返回安装

machina-driving

Drive a Machina state machine to a deterministic outcome on behalf of an AI agent. USE WHEN: a task is governed by a state machine (a machine definition JSON with states, transitions, guards, actions, tools, checks, scenarios); executing a workflow that must be deterministic and auditable; running a skill whose SKILL.md declares a `machina:` machine; firing events, checking status, satisfying evidence checks, verifying run integrity with `check`, or producing a terminal report for a machine-driven run; escalating a STUCK run to a human conductor. DO NOT USE FOR: authoring or scoring machine definitions (use machina-authoring); modifying the Machina simulator app or its engine (use machina-simulator); implementing or modifying the driver/runtime tooling such as `scripts/machine-driver.py` (engine development) unless you are a maintainer of this skill upgrading the driver itself; general diagramming or XState/SCXML authoring.

2026-09-09

machina-authoring

Author valid, high-scoring state machines in Machina machine JSON format (spec v3.0.0 / v2.0.0 / v1.0.0). USE WHEN: writing or generating a machine definition (states, transitions, guards, actions, context, scenarios); modeling a real workflow (order fulfillment, refunds, signup, retries) as a Machina state machine; fixing or upgrading a machine JSON for validation or higher compliance score; explaining validation failures or low scores; running the bundled machina-validator.py CLI to validate, score, or generate gaps/scenarios; adding retry guards or cycle protection; or preparing machines for the compliance scorer ("Excellent" ≥90). DO NOT USE FOR: modifying the Machina simulator app, its engine, UI, or SPEC_REGISTRY (use machina-simulator-maintenance), debugging machine-validator.py scripts, XState config authoring, SCXML documents, or general diagramming.

2026-09-08

copilot-cli-subsession

Spawn a new isolated Copilot CLI sub-session from a main Copilot CLI or VS Code session. Use when you need to programmatically create, resume, or chain Copilot CLI sessions with explicit control over session ID, custom agent, model, BYOK provider profile, permissions, and working directory. Triggers: "invoke copilot", "spawn copilot", "copilot sub-session", "programmatic copilot cli", "programmatic copilot subprocess", "copilot cli session id", "resume copilot session", "chain copilot sessions", "isolated copilot session", "subagent copilot cli", "task copilot cli".

2026-09-07

查看这个仓库的全部 Skills

issue-md-writer

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills