seis-governance

Validates SEIS repository governance, marketplace policy, and release readiness against canonical manifests.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-governance-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-governance
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis-ai-agent/skills/seis-governance
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-governance-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unsafe or inconsistent changes to the SEIS repository by enforcing governance rules, identity checks, and release gating before any policy- or release-facing modification is applied. ## Core Features & Use Cases - Governance Workflow Enforcement: Checks git status, branch context, and repository identity against canonical manifests like .agents/plugins/marketplace.json and data/seis-operating-identities.json before changes. - Release Decision Gating: Blocks readiness claims until plugin checks, quality gates, and GitHub reviews pass for release-facing files. - Marketplace & Identity Validation: Verifies plugin install IDs, lane consolidation, and operating identities using npm check scripts. - Use Case: Before publishing a SEIS plugin update, run the governance checks to confirm the marketplace manifest, agent profile, and branch policy all align with the canonical main branch. ## Quick Start Ask the agent to validate the current SEIS repository state against governance policy and report whether the plugin is ready for release.

Frequently Asked Questions about seis-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate SEIS repository governance before a release?▼

Run the governance checks with npm scripts such as check:open-source-governance, check:seis-repo-marketplace, and check:seis-ai-agent. The skill compares repository state against canonical manifests and only allows readiness claims after all gates pass.

What files define SEIS marketplace and identity policy?▼

The canonical sources are .agents/plugins/marketplace.json, data/seis-operating-identities.json, and data/installed-codex-plugins-2026-06-15.json. Plugin expectations are validated against scripts/install-seis-ai-agent.mjs and the agent-profile.json asset.

Can I publish a standalone lane ID as a separate marketplace plugin?▼

No. Former standalone lane IDs are retired, and all current lane access resolves through the primary install ID seis-ai-agent@seis-repo. Legacy personal plugin IDs remain only as compatibility aliases.

When is a SEIS release considered ready?▼

Readiness requires the seis-ai-agent plugin checks to pass with lane readiness, npm run quality to pass or a user-approved reduced scope, and GitHub checks reviewed if repository-facing files changed. No apply or deployment action completes without explicit confirmation.

Does the governance workflow modify uncommitted local changes?▼

No. The operating rules require preserving user work and never discarding uncommitted local edits. Git status and branch context are inspected before any governance or release-facing change.