Map internal corporate author identities (name + email) to public github.com identities using MCP-driven user lookup, then rewrite git history with git-filter-repo + .mailmap. Specific to CNCF OSS migration workflows.
Inject and validate the legal and governance documents required for a CNCF-compliant open-source project: Apache 2.0, DCO, GOVERNANCE, SECURITY, CODE_OF_CONDUCT, and README hygiene. Specific to CNCF OSS migration.
Technically migrate a clean repository from GitHub Enterprise Server (GHES) to a public github.com org using squash-to-milestones or mirror-push, then configure branch protection and least-privilege RBAC. Specific to CNCF OSS migration.
Integrate CNCF CLOMonitor and OpenSSF Scorecard into CI/CD to continuously validate open-source project health after a GHES-to-github.com migration. Specific to CNCF OSS migration post-validation workflows.
Scan and strip hardcoded secrets, internal credentials, corporate hostnames, and proprietary naming from a GitHub Enterprise repo before it goes public. Specific to the Vionix CNCF migration workflow — do not use for general code review.
Create a new reusable composite GitHub Action with well-defined inputs/outputs that can be used by customer workflows.
File a Vionix LookinGlass mirror request for a github.com GitHub Action by filling out the IssueOps form at https://<git-host>/github/vionix-lookinglass/issues/new?template=mirrorrepo.yaml. Use this skill whenever the user asks to mirror a github.com repo/action into <git-host>, to "create a mirror request", "onboard a github action", or mentions vionix-lookinglass mirror issues — even if they only provide the upstream URL. It maps the user's intent to every form field, submits the issue with the gh CLI, and explains the follow-up IssueOps commands (@vionix validate, @vionix lgtm) and the GHAS exposed-secrets resume flow.
Development rules for the Vionix DevSecOps platform repositories (vionix-github-workflows, github/vionix-lookinglass, vionix-devsecops-apps): PR conventions (Jira/PRD title prefixes; labels, project, and assignee required on agentic PR creation), the GitHub rule that workflow_dispatch workflows MUST be merged to the default branch before they can be triggered, and how to land stacked PRs through the merge queue. Use this skill whenever creating branches or PRs agentically, introducing or testing a workflow_dispatch/schedule workflow, or merging PRs in these repositories.