ドキュメント・Officeのスキル

Author and modify documentation for projects that use Gehtsoft's docgen utility. Use this skill whenever the user mentions docgen, .ds files, the doc/ directory of a repository, project.xml or project.proj for documentation, or wants to write/edit/build/debug API documentation in any codebase that uses docgen. Also use it whenever the user asks about generating C#, C++, or Java API documentation that follows Gehtsoft conventions, even if they don't say "docgen" explicitly.

日本語の概要は準備中です。原文の説明を表示しています。

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch.

日本語の概要は準備中です。原文の説明を表示しています。

Use when filing one or more GitHub issues for planned work — "file an issue for this", "turn this plan into issues", "open a tracking issue". Covers filing everything on skyf0xx/hedgehog regardless of which repo's code changes, whether to split a plan into a tracking issue plus sub-issues, which account files the issue, labels, and acceptance criteria. For how to word an issue, see the pr-writing skill.

日本語の概要は準備中です。原文の説明を表示しています。

Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

日本語の概要は準備中です。原文の説明を表示しています。

Apply MCAF documentation guidance for docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.

日本語の概要は準備中です。原文の説明を表示しています。

Create or refine durable engineering documentation: docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Generates MkDocs-flavored or standard GitHub-flavored Markdown documentation from codebase analysis findings including API references, architecture guides, standalone markdown files, and change summaries (converted from agent)

日本語の概要は準備中です。原文の説明を表示しています。

Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, or any visual documentation in markdown.

日本語の概要は準備中です。原文の説明を表示しています。

Documentation management workflow for MkDocs sites and standalone markdown files -- initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".

日本語の概要は準備中です。原文の説明を表示しています。

Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries.

日本語の概要は準備中です。原文の説明を表示しています。

Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".

日本語の概要は準備中です。原文の説明を表示しています。

Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, visualizations, or any visual documentation in markdown. Always use this skill when generating or updating Mermaid code blocks.

日本語の概要は準備中です。原文の説明を表示しています。

Validates adapter files against live platform documentation to detect stale mappings,missing features, and outdated version information

日本語の概要は準備中です。原文の説明を表示しています。

Hunt full Account Takeover (ATO) by chaining lower-severity findings — IDOR-to-email-disclosure, password-reset-token-theft, OAuth-redirect-uri abuse, response-manipulation, cookie scope, CRLF in Set-Cookie, race-condition on signup. Use when the user wants to escalate small findings to ATO or thinks an ATO path exists.

日本語の概要は準備中です。原文の説明を表示しています。

Hunt Server-Side Template Injection (SSTI) in Jinja2, Twig, Freemarker, Velocity, Smarty, ERB, Handlebars, Mustache, and Spring (SpEL). Use when input is reflected in a way that suggests template rendering — error pages, email templates, PDF generators, dynamic content systems.

日本語の概要は準備中です。原文の説明を表示しています。

Helps with documents.

日本語の概要は準備中です。原文の説明を表示しています。

Fill interactive PDF forms (AcroForm) with user-provided data, verify every field, and deliver a flattened copy. Use when the user asks to fill in, complete, or populate a PDF form, provides data alongside a fillable PDF, or mentions PDF form fields, checkboxes, or dropdowns. Do not use for creating PDFs from scratch, merging or splitting PDFs, or scanned/image-only forms with no interactive fields - for those, tell the user this skill cannot help and suggest an OCR-based approach instead.

日本語の概要は準備中です。原文の説明を表示しています。

Generate or update a CHANGELOG.md from merged commits and pull requests, grouped by change type and written for end users. Use when the user asks to write release notes, update the changelog, or summarize what changed between two versions or tags. Do not use for writing individual commit messages or for API-reference documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Convert a Markdown outline into a presentation-ready HTML slide deck with consistent theming and speaker notes. Use when the user asks to turn notes, an outline, or a document into slides, or mentions a talk, deck, or presentation built from Markdown. Do not use for .pptx files - that is a different workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Format technical PDF reports using company layout rules. Use when asked to clean up, standardize, or prepare inspection reports, equipment manuals, or engineering reports. Do not use for legal contracts or general writing.

日本語の概要は準備中です。原文の説明を表示しています。

Translate technical documentation between Russian and English while preserving Markdown structure, code blocks, and established terminology. Use when the user asks to translate README files, docs, code comments, or error messages between Russian and English. Do not use for literary translation or for other language pairs.

日本語の概要は準備中です。原文の説明を表示しています。

Update documentation after code changes. Scans git diff to find affected docs and updates them for consistency.

日本語の概要は準備中です。原文の説明を表示しています。

Create a new documentation file following project standards. Detects overlap with existing docs before creating.

日本語の概要は準備中です。原文の説明を表示しています。