技能 write-feature-docs

📦

write-feature-docs

Name: write-feature-docs
Author: warpdotdev

內容修訂 r1 高風險 ⚙️ 外部命令🌐 網路存取📁 檔案系統存取🔑 環境變數

Draft Warp Feature Documentation

Feature specifications do not automatically become accurate, publishable documentation. This skill verifies implementation details, confirms audience and structure, drafts MDX, and prepares a reviewable pull request.

支援: Claude Codex Code(CC)

⚠️ 38 差

Maintain this Skill? Claim it ⚠️ 38 差

安裝前請停止並請求確認。

請審查安裝計畫，並在變更檔案前取得使用者明確同意。

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "write-feature-docs" from https://skillstore.io/skills/warpdotdev-write-feature-docs.md and its manifest at https://skillstore.io/api/skills/warpdotdev-write-feature-docs/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/warpdotdev-write-feature-docs.md 已簽名 manifest GET /api/skills/warpdotdev-write-feature-docs/manifest 已簽名 lockfile GET /api/skills/warpdotdev-write-feature-docs/lockfile

測試它

正在使用「write-feature-docs」。 Document APP-1234 from its product and technical specifications.

預期結果:

A confirmed content design plan, a concise outline with verification labels, and a complete MDX feature page ready for review.

正在使用「write-feature-docs」。 Create documentation for a shipped feature that has no specification.

預期結果:

A research summary, targeted questions for unresolved behavior, and a documentation draft based on confirmed repository evidence.

正在使用「write-feature-docs」。 Update the existing Agent Mode page and prepare a draft pull request.

預期結果:

An updated MDX page following Warp style and template rules.
Validated screenshots or explicit reviewer placeholders.
A draft pull request containing the content plan and unresolved review items.

安全審計

高風險

v1 • 2026/9/4 開啟版本化報告

Most detections are Markdown backticks, code fences, relative links, or benign GitHub examples and are false positives. The fixed pull request body path creates a local tampering risk, and optional UI capture can expose sensitive data when images enter a public documentation change. No prompt injection or malicious intent was found.

已掃描檔案

464

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (1)

高

SKILL.md:19

Screen capture upload

5.5. Attempt screenshot capture via computer use (if available)

The skill directs computer-use capture of product UI and later places accepted images in a public documentation change. Its privacy checklist reduces, but cannot eliminate, accidental disclosure.

能力複核項目 (2)

這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。

中

SKILL.md:411

Temp directory access

Write the body to `/tmp/pr-body.md` using whatever file-writing method is available (a file-creation

The workflow writes sensitive pull request content to a fixed shared path, /tmp/pr-body.md. A stale file or symbolic-link race could alter content or overwrite another writable target.

中

SKILL.md:413

Temp directory access

gh pr create --draft --body-file /tmp/pr-body.md ...

The command uploads content from the predictable /tmp/pr-body.md path. Another local process could replace that file before gh reads it, causing unintended pull request content.

風險因素

⚙️ 外部命令 (50)

🌐 網路存取 (2)

SKILL.md:69 SKILL.md:72

📁 檔案系統存取 (5)

SKILL.md:214 SKILL.md:215 SKILL.md:358 SKILL.md:411 SKILL.md:413

🔑 環境變數 (1)

SKILL.md:102

偵測到的模式

Screen capture upload

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/warpdotdev-write-feature-docs/security.svg)](https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-write-feature-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/warpdotdev-write-feature-docs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

學術引用 (APA · BibTeX · CFF)

APA 引用

warpdotdev. (2026). write-feature-docs security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1

BibTeX 引用

@techreport{warpdotdev-warpdotdev-write-feature-docs-2026,
  author = {warpdotdev},
  title = {write-feature-docs security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "write-feature-docs security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "warpdotdev"
date-released: "2026-09-04"
url: "https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1"
identifiers:
  - type: other
    value: "skillstore:warpdotdev-write-feature-docs:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

Document a shipped feature

Convert an approved product or technical specification into an accurate first-pass documentation page.

Reduce documentation research

Verify implementation details and isolate only the questions that require subject matter expertise.

Prepare a reviewable update

Create or update an MDX page and open a structured draft pull request for editorial review.

試試這些提示

Draft from a specification

Draft documentation for Warp feature [name] using spec [ID]. Find PRODUCT.md and TECH.md, then present the content design plan.

Research a feature without a spec

Research feature [name] without a spec. Verify behavior in [repository], identify unknowns, and ask only targeted questions before planning the page.

Update an existing page

Document [feature] using [spec ID]. Prefer updating [existing page], verify UI paths, then present the content plan and outline separately.

Prepare the full review workflow

Prepare a draft documentation pull request for [feature]. Verify release readiness, sanitize screenshots, list unverified claims, and include the confirmed content design plan.

最佳實務

Keep the engineer present for separate content plan and outline confirmations.
Validate feature and specification tokens before using them in shell or GitHub searches.
Mark unresolved claims clearly and exclude confidential implementation details from public drafts.

避免

Do not run the workflow unattended or combine the two required confirmation stages.
Do not publish technical specification details before an engineer confirms they are public.
Do not include screenshots containing private repositories, credentials, personal information, or customer data.

常見問題

Does this skill work without a product specification?

Yes. It researches the relevant repository first, then asks targeted questions about gaps that code cannot resolve.

Can this skill run automatically after every release?

No. It requires an interactive engineer. Warp uses the separate missing_docs workflow for release-triggered documentation.

Which documentation formats does it produce?

It produces MDX pages based on Warp templates for feature, conceptual, procedural, reference, troubleshooting, quickstart, or guide content.

How does it protect confidential technical information?

It flags internal implementation details from TECH.md and requires engineer confirmation before including them in public documentation.

Are screenshots required?

No. Screenshot capture is optional. Failed, unavailable, unsafe, or unverified captures remain explicit placeholders for a documentation reviewer.

What access does the workflow require?

It needs relevant repository access and GitHub CLI authentication. Screenshot capture also needs an available computer use tool.

開發者詳細資訊

作者

warpdotdev

授權

MIT

Skillstore 修訂

版本提示

作者未聲明版本。

儲存庫

https://github.com/warpdotdev/common-skills/tree/b811c24365ae505bfc9646458957b886e29110b5/.agents/skills/write-feature-docs

引用

e5464e662405de6361fdde6b984f9ea865635f64

維護新鮮度

2026/9/8

使用量

0 次下載 · 0 次瀏覽

檔案結構

📄 SKILL.md

warpdotdev 的更多技能

查看全部

📦

council

Compare Decisions with an AI Council

Complex decisions can suffer from narrow analysis and hidden assumptions. This skill coordinates diverse agents, compares their evidence, and produces one actionable recommendation.

效率查看

📦

spec-driven-implementation

Plan Features With Living Specs

Substantial feature work can become ambiguous when product intent, technical decisions, and implementation drift apart. This skill guides agents through practical product and technical specifications that stay aligned with shipped work.

程式開發查看

📦

migrate-to-factory

Migrate Workflows to Factory

Moving an existing agent workflow into Factory can create duplicate roles, broken paths, or conflicting handoffs. This skill guides a focused migration into an existing Factory repository and validates the resulting configuration.

DevOps 與基礎設施查看

📦

respond-to-pr-comments-in-blocklist

Resolve Pull Request Feedback Safely

Pull request feedback can be difficult to track, implement, and answer consistently. This skill guides each decision, validates accepted changes, and previews GitHub responses before posting.

程式開發查看

📦

write-product-spec

Write Clear Product Specifications

Turn ambiguous feature requests into structured product specifications that align design, engineering, and review. This skill defines user-visible behavior, scope, references, open questions, and handoff details in a consistent PRODUCT.md format.

效率查看

📦

diagnose-ci-failures

Diagnose CI Failures Faster

CI failures can hide the first useful error among checks, logs, and repeated noise. This skill gathers relevant GitHub evidence and produces a prioritized plan for repair.

DevOps 與基礎設施查看

查看全部

📦