seis-github-workflow

Govern GitHub branch, pull request, and CI check workflows for SEIS repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working on the SEIS repository risk claiming GitHub readiness without evidence, mixing local check results with GitHub check results, or bypassing branch and review governance. This Skill enforces a disciplined workflow so branches, pull requests, CODEOWNERS, and CI checks stay aligned with GitHub as the source of truth. ## Core Features & Use Cases - Branch and PR Governance: Keeps main as the only permanent branch and routes changes through short-lived branches, PR templates, and CODEOWNERS review. - Evidence-Based Readiness: Requires inspecting branch protection, PR state, check runs, and workflow runs before claiming anything is pushed, merged, or protected. - Governance Check Routing: Directs Master Prompt and governance changes through the issue template, PR template, CI workflow, and local check scripts such as check-seis-master-prompt and check-open-source-governance. - Use Case: When preparing a governance change to the SEIS repo, use this Skill to plan the branch, run the focused local checks, open a PR with the correct template, and leave an explicit no-push gate if GitHub evidence is unavailable. ## Quick Start Use the SEIS GitHub workflow skill to plan a branch and pull request for my governance change and tell me which local checks and GitHub evidence I need before claiming readiness.

Frequently Asked Questions about seis-github-workflow

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

FAQPage Schema
How do I verify GitHub checks passed before claiming a PR is ready?▼

Inspect the actual GitHub evidence: PR state, check runs, and workflow runs for the commit. A local check pass is not proof that GitHub checks passed, so prefer workflow runs or commit check-runs over unavailable code-scanning endpoints.

How should branches and pull requests be structured in the SEIS repository?▼

Keep `main` as the only permanent branch and use short-lived branches or PRs only as review and integration staging. Route changes through the PR template and CODEOWNERS review before merging.

What local checks should run before a SEIS governance change?▼

Run the focused checks first: `npm run check:seis-master-prompt-report`, `npm run check:seis-master-prompt`, and `npm run check:open-source-governance`. Escalate to `npm run quality` when package scripts, workflows, plugin metadata, or public docs change.

What should I do when GitHub API access or auth is unavailable?▼

Leave an explicit no-push or no-readiness gate instead of claiming completion. Never claim pushed, merged, deployed, connected, ready, or protected without inspecting current external state.

Can I delete branches or repositories after merging a SEIS change?▼

Only after verified merge or import evidence and explicit maintainer approval. Deleting branches or source repositories without that evidence violates the workflow's evidence rules.