菜单
Fetches the latest content from styleguide.dynatrace.com and updates the vendored reference docs in this plugin. Run when the Dynatrace style guide has been updated and you want the latest rules. Activated when the user prompt starts with "dt-style-refresh".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Jira-driven release-notes drafting. Reads a Value Increment (or any ticket) from exported markdown, optionally grounds in PR diffs, renders a dynatrace-docs release-notes body, runs a light dt-style-checker gate, and writes a persistent draft to paste into Jira's release-notes field. Activated when the user prompt starts with "release-notes:".
Architecture-authoring workflow (Product Architect phase, sub-project 3 of the VI-creation flow). Grounds on the mounted implementation repos (architect-driven discovery — no PRs) and authors an ARD for a VI (create-ard: <VI-KEY>) or an Epic (create-ard: <VI-KEY> <Epic-KEY>, inheriting the VI-level ARD), against _shared/ard-format.md, gated by the Opus ard-reviewer, written to $SPECS_PATH/specifications/<KEY>-<slug>/. Optional; scoped; product-architecture level (no code writing). Introduces the pa role. Activated when the user prompt starts with "create-ard:".
VI-creation workflow (PM phase, sub-project 2 of the VI-creation flow). Turns a refined idea.md + a user-supplied JIRA-KEY into a high-quality Value Increment document (spine + adapt-in profiles: --lean|--hybrid|--full), authored via a relentless grill against _shared/vi-format.md, gated by the Opus vi-reviewer, written to $SPECS_PATH/specifications/<KEY>-<slug>/ and published to Jira by paste + re-import. Product-level (no code scan). Offers release-notes: and create-ard: as next steps. Activated when the user prompt starts with "create-vi:".
VI-update workflow (PM phase) — refresh/re-do an existing Value Increment. Resolves the VI Jira-import-first (source of truth) with a 3-day freshness gate, grounds on the VI + comments + any ARD/spec/transcript, updates it via a relentless grill against _shared/vi-format.md, gated by the Opus vi-reviewer, and writes canonical + archived revisions to $SPECS_PATH/specifications/<KEY>-<slug>/. Product-level (no code scan). Activated when the user prompt starts with "update-vi:".
Jira-driven feature-documentation workflow. Phase 0 preflight-discovers the docs repo + profile (in-repo → built-in dynatrace-docs default → on-demand docs-profile:) and the VI's specs dir under /workspace. Phase 4.5 determines/confirms the applicable space(s). Optional saas|managed constraint scopes the run to one space. Reads a Value Increment hierarchy from exported markdown, resolves PR diffs in parallel, synthesises product documentation, and gates on style-check and Opus doc review. Optional --counterpart <JiraID|PR-url> grounds a space-constrained run on the other space's existing docs (read-only). Activated when the user prompt starts with "document:".
Scan the vault (or a target directory) for tags used in page frontmatter and page bodies, diff against the vault's .obsidian/copilot/tag-index.md, prompt the user to approve new tags and clean stale ones, then update tag-index.md in place. Run after heavy ingest or other large content changes when new concepts may have introduced new tags. Triggers on: wiki-tags-refresh, refresh tags, update tag index, wiki tags, sync tags.
基于 SOC 职业分类
| name | dt-style-refresh |
| description | Fetches the latest content from styleguide.dynatrace.com and updates the vendored reference docs in this plugin. Run when the Dynatrace style guide has been updated and you want the latest rules. Activated when the user prompt starts with "dt-style-refresh". |
| allowed-tools | view, web_fetch, bash, edit |
Updates the vendored reference docs in this plugin from the Dynatrace style guide website. Use when you suspect the style guide has changed and the local references are stale.
Fetch the following URLs and extract actionable rules:
| Reference file | Source URLs |
|---|---|
terminology.md | https://styleguide.dynatrace.com/docs/dynatrace-terminology, https://styleguide.dynatrace.com/docs/dynatrace-trademarks |
word-list.md | https://styleguide.dynatrace.com/docs/word-list |
voice-and-tone.md | https://styleguide.dynatrace.com/docs/style/voice-and-tone |
grammar.md | https://styleguide.dynatrace.com/docs/style/grammar |
formatting.md | https://styleguide.dynatrace.com/docs/style/numbers, https://styleguide.dynatrace.com/docs/style/punctuation, https://styleguide.dynatrace.com/docs/style/lists, https://styleguide.dynatrace.com/docs/style/titles-and-headings, https://styleguide.dynatrace.com/docs/style/acronyms, https://styleguide.dynatrace.com/docs/style/date-and-time, https://styleguide.dynatrace.com/docs/style/link-text, https://styleguide.dynatrace.com/docs/style/emoji |
ui-interactions.md | https://styleguide.dynatrace.com/docs/style/ui-interactions |
accessibility.md | https://styleguide.dynatrace.com/docs/accessibility-and-inclusivity/inclusive-language, https://styleguide.dynatrace.com/docs/accessibility-and-inclusivity/internationalization |
top-10-tips.md | https://styleguide.dynatrace.com/docs/best-practices/top-10-tips, https://styleguide.dynatrace.com/docs/best-practices/write-for-answer-engine-optimization |
For each reference file:
Write updated reference docs to:
~/.copilot/installed-plugins/ihudak-copilot-plugins/dt-style-guide/references/
Summarise what changed in each file:
If nothing changed, report that the references are already up to date.
dt-style-guide/references/)
are not modified. To persist changes to the repo, copy the refreshed files
back into the plugin source at dt-style-guide/references/ and commit.max_length
and use pagination (start_index) if content is cut off.