janpereira-dev/ngautopilot/angular-architecture-micro-frontends-release-governance

Claude Code and agent skill by janpereira-dev/ngautopilot

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Reviews release governance for Angular micro-frontends in Nx monorepos, focusing on ownership, versioning, deployment independence, compatibility checks, and coordinated rollout policy.

Install

npx vskill@latest install janpereira-dev/ngautopilot/angular-architecture-micro-frontends-release-governance

SKILL.md

The same SKILL.md was published earlier as janpereira-dev/ngautopilot/angular-architecture-micro-frontends-release-governance.

Micro-frontends Release Governance

Purpose

Use this skill to review or design release governance for Angular micro-frontends.

Micro-frontends only work sustainably when ownership, versioning, deployment policy, and compatibility checks are explicit. This skill focuses on the operational controls that keep independent delivery safe.

The core rule is simple:

txt
Independent deployment requires explicit release governance.

When to Use

Use this skill when:

  • remotes are released independently
  • teams need versioning and compatibility policy
  • rollout and rollback need coordination
  • shell and remote release timing differs
  • CI/CD gates must protect runtime composition

Do

Define the release contract:

txt
Owner:
Remote:
Version:
Deployment target:
Compatibility range:
Rollback strategy:
Approval gate:
Smoke tests:

Coordinate shell and remote compatibility:

txt
shell v1 + remote v1 -> supported
shell v1 + remote v2 -> supported
shell v1 + remote v3 -> blocked

Use release policy that matches the delivery model:

txt
Shared release train -> simpler governance
Independent remotes -> stricter compatibility gates

Do Not

Avoid shipping a remote without an owner.

Avoid version drift without compatibility checks.

Avoid independent deployment without rollback policy.

Avoid approving releases only on the basis of build success.

Review Checklist

  • [ ] Each remote has an owner.
  • [ ] Version compatibility is documented.
  • [ ] Rollback strategy exists.
  • [ ] Smoke tests gate the release.
  • [ ] Shell and remote compatibility is validated.
  • [ ] The release policy matches the actual team topology.

Expected Output

  1. Identify the release model.
  2. Check ownership and version policy.
  3. Flag compatibility risks.
  4. Recommend rollout and rollback controls.
  5. Define the smallest safe release governance model.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
4
Repository forks
1
7-day trend score
13

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/janpereira-dev/ngautopilot/angular-architecture-micro-frontends-release-governance/badge)](https://verified-skill.com/skills/janpereira-dev/ngautopilot/angular-architecture-micro-frontends-release-governance)

Something wrong with this skill or its page? Tell us.