Initial curated ITWorx_MCP_Hub source from 368fba691ea8d23403b4d56b53b5ec670d7c5020

2026-10-01 01:36:21 +02:00
commit cb5be898ea
@@ -0,0 +1,39 @@
+---
+name: portfolio-engineer
+description: "Plan and deliver one consistent, reviewable change across an explicit bounded set of registered ITWorx Gitea repositories. Use for multi-repository maintenance, dependency alignment, policy updates, or coordinated migrations; do not use for a single-repository change."
+---
+
+# Portfolio Engineer
+
+Treat every repository as an independent review and rollback boundary.
+
+1. Start with the requested portfolio operation. Do not call capabilities,
+   connection or self-test tools as routine preflights. Use them only after a
+   concrete catalog-drift or connectivity error. Reuse established exact
+   `repositoryRef` values and list repositories only when scope is unknown;
+   never infer references from display names.
+   For an issue inventory across repositories, call `gitea.issue.search`
+   directly and pass repositories the user wants ignored through
+   `excludeRepositoryNames`; do not fetch repository metadata first.
+2. Audit the explicit set with `gitea.portfolio.health`; keep each batch at 25
+   repositories or fewer.
+3. For repository governance, call `gitea.portfolio.governance.preview` for at
+   most 25 repositories. Apply only unchanged plan hashes with
+   `gitea.portfolio.governance.apply`, at most five repositories per call, and
+   finish each batch with `gitea.portfolio.governance.verify`. Do not dispatch
+   validation during rollout; the managed workflow is pull-request/dispatch only.
+4. Call `gitea.orchestration.plan` for at most ten repositories. Review every
+   default-branch SHA, generated `codex/*` branch and the returned plan ID before
+   starting.
+5. Call `gitea.orchestration.start` only with the unchanged plan ID. A retry may
+   resume existing safe branches; never delete or overwrite them to force a retry.
+6. Inspect, preview, apply and validate each repository independently. Use
+   `gitea.workspace.status` to resume after interruption and open a separate PR
+   per repository.
+7. Stop an individual repository on conflict or failed validation while safely
+   continuing unrelated repositories. Report partial results explicitly.
+8. Merge each exact validated PR head through the governed tool when server-side gates pass. Ask for confirmation before merged-branch deletion.
+
+Do not use arbitrary commands, force pushes, ad-hoc default-branch writes,
+repository administration, or one bulk merge action. The plan-locked governance
+tool is the only exception for its fixed managed workflow and protection contract.
@@ -0,0 +1,7 @@
+interface:
+  display_name: "ITWorx Portfolio Engineer"
+  short_description: "Coordinate reviewed changes across Gitea repos"
+  brand_color: "#3056D3"
+  default_prompt: "Use $portfolio-engineer to plan and deliver this change across the selected Gitea repositories."
+policy:
+  allow_implicit_invocation: true