tibco-developer-hub

Produce a detailed change-impact analysis for a TIBCO Developer Hub catalog entity (API, Component, Resource, System) by reading its real dependency graph from the running Developer Hub via the catalog REST API, classifying every related entity into impact tiers, and writing a report plus color-coded integration-topology Mermaid diagrams into the impact_analysis/ folder. Trigger when the user wants an impact analysis, a blast-radius assessment, "what breaks if I change X", a dependency/ripple analysis, who-consumes-this, or a coordination/ownership view before modifying a catalog entity.

Author a new TIBCO Developer Hub import flow template. Trigger when the user wants to create an import flow, add a new import-flow template, build a BWCE/BW6/BW5/Flogo/EMS importer, or scaffold an entry that ingests existing source repositories into the Developer Hub catalog. Distinct from create-template: import flows follow the clone→extract→generate→register pattern and use TIBCO custom actions (tibco:git:clone, tibco:extract-parameters, tibco:create-yaml, tibco:git:push). Writes the Template entity YAML (and optional Nunjucks entity skeletons) under templates/<slug>/ and registers it in app-config.local.yaml so it appears at /import-flow after a backend restart.

Author a new Backstage scaffolder template for this TIBCO Developer Hub repo. Trigger when the user wants to create a new software template, add a scaffolder template, write a BWCE/Flogo/import-flow template, or scaffold a new entry under the templates/ folder. Gathers metadata + parameters + steps via AskUserQuestion, writes the Template entity YAML plus a starter `skeleton/` (with `catalog-info.yaml`) under `templates/<slug>/`, and registers the file under `catalog.locations` in `app-config.local.yaml` so it appears in the Software Templates picker after a backend restart.

Create or replace a Backstage theme in this Developer Hub app, with an optional custom logo. Trigger when the user wants to add a new color theme, rebrand the app, change the sidebar logo, replace the default TIBCO theme, or create a customer-branded variant. Gathers palette/font/logo via AskUserQuestion, writes theme file(s) under packages/app/src/themes/, registers them in packages/app/src/App.tsx, wires the theme-aware logo swap in packages/app/src/components/Root/Root.tsx, type-checks with yarn tsc, and verifies in the browser via playwright when the dev server is running.

Bootstrap a fresh local TIBCO Developer Hub dev environment end-to-end. Trigger when the user wants to set up / initialize / bootstrap the project for the first time, get the app running locally, or onboard a new machine. Verifies prerequisites and versions (Node, Yarn, native build toolchain; Docker only if a Postgres DB is chosen), creates app-config.local.yaml and .env.yarn from their templates, lets the user pick an in-memory (better-sqlite3) or Docker Postgres database, optionally wires a GitHub PAT, then runs yarn install and starts the app, confirming the ports are listening.

Test an import flow template in two phases: (1) dry-run structure validation — same mechanics as test-template — to verify YAML syntax and Nunjucks skeleton rendering without any real GitHub activity; (2) live scaffolder task execution against a real GitHub repository, followed by Backstage catalog API verification that the imported entities were actually registered in the Developer Hub. Trigger when the user wants to test an import flow, verify catalog import, run an import flow end-to-end, check that components were registered after an import, or confirm a newly created import flow works correctly.

Dry-run a Backstage scaffolder template against the running backend and write the rendered files into `template-workspace/dry-run-<N>/` for inspection. Trigger when the user wants to test a template, preview template output, dry-run a template, see what a template generates, or debug a `${{ values.* }}` substitution — without actually creating a GitHub repo. Picks the template from `templates/`, prompts for parameter values via AskUserQuestion, ensures the backend body limit is high enough, POSTs to `/api/scaffolder/v2/dry-run` (gzipped, since the skeleton can be MBs), and unpacks the response.