Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

api-guideline-reviewer

Sterne0

Forks1

Aktualisiert13. Juli 2026 um 16:03

Review OpenAPI specification files against Dynatrace REST API and IAM permission naming guidelines. Checks version consistency, naming conventions, IAM scope format, HTTP status codes, and schema composition. Activated when the user prompt starts with "api-guideline-reviewer:".

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

ihudak

ihudak/ihudak-copilot-plugins

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

Datei-Explorer

26 Dateien

SKILL.md

readonly

name	api-guideline-reviewer
description	Review OpenAPI specification files against Dynatrace REST API and IAM permission naming guidelines. Checks version consistency, naming conventions, IAM scope format, HTTP status codes, and schema composition. Activated when the user prompt starts with "api-guideline-reviewer:".
allowed-tools	view, bash, glob, grep, task, web_fetch, ask_user

Review OpenAPI specification files for compliance with Dynatrace REST API and IAM permission naming guidelines: the argument (text following the api-guideline-reviewer: trigger)

If the argument (text following the api-guideline-reviewer: trigger) is empty, ask the user which OpenAPI spec file(s) to review.

Dispatch the review to the api-guideline-reviewer subagent:

→ task(agent_type: "dev-workflows:api-guideline-reviewer"):

"Review the following OpenAPI spec file(s) against the guidelines: the argument (text following the api-guideline-reviewer: trigger)"

Surface the subagent's verdict to the user.

Mehr aus diesem Repository

gleiches Repository

release-notes

ihudak/ihudak-copilot-plugins

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:".

2026-07-170

create-ard

ihudak/ihudak-copilot-plugins

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:".

2026-07-170

create-vi

ihudak/ihudak-copilot-plugins

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:".

2026-07-170

update-vi

ihudak/ihudak-copilot-plugins

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:".

2026-07-170

document

ihudak/ihudak-copilot-plugins

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:".

2026-07-160

wiki-tags-refresh

ihudak/ihudak-copilot-plugins

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.

2026-07-140

name	api-guideline-reviewer
description	Review OpenAPI specification files against Dynatrace REST API and IAM permission naming guidelines. Checks version consistency, naming conventions, IAM scope format, HTTP status codes, and schema composition. Activated when the user prompt starts with "api-guideline-reviewer:".
allowed-tools	view, bash, glob, grep, task, web_fetch, ask_user

Review OpenAPI specification files for compliance with Dynatrace REST API and IAM permission naming guidelines: the argument (text following the api-guideline-reviewer: trigger)

If the argument (text following the api-guideline-reviewer: trigger) is empty, ask the user which OpenAPI spec file(s) to review.

Dispatch the review to the api-guideline-reviewer subagent:

→ task(agent_type: "dev-workflows:api-guideline-reviewer"):

"Review the following OpenAPI spec file(s) against the guidelines: the argument (text following the api-guideline-reviewer: trigger)"

Surface the subagent's verdict to the user.