| name | git-pr-workflows-onboard |
| description | Onboard workflow skill. Use this skill when the user needs to onboard a repository, start a new contributor safely, verify setup and access, map the contribution path, or prepare a clean handoff while preserving upstream workflow, copied support files, and provenance. |
| version | 0.0.1 |
| category | devops |
| tags | ["git-pr-workflows-onboard","onboarding","repository-onboarding","developer-setup","knowledge-transfer","handoff","access-review","contribution-workflow","omni-enhanced"] |
| complexity | advanced |
| risk | caution |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | omni-team |
| author | Omni Skills Team |
| license | Unknown |
| date_added | 2026-04-15 |
| date_updated | 2026-05-10 |
| source_type | omni-curated |
| maintainer | Omni Skills Team |
| family_id | git-pr-workflows-onboard |
| family_name | Onboard |
| variant_id | omni |
| variant_label | Omni Curated |
| is_default_variant | true |
| derived_from | skills/git-pr-workflows-onboard |
| upstream_skill | skills/git-pr-workflows-onboard |
| upstream_author | sickn33 |
| upstream_source | community |
| upstream_pr | 271 |
| upstream_head_repo | diegosouzapw/awesome-omni-skills |
| upstream_head_sha | 93ab394af5645f7127d5003ee02c9566ae5353cd |
| curation_surface | skills_omni |
| enhanced_origin | omni-skills-private |
| source_repo | diegosouzapw/awesome-omni-skills |
| replaces | ["git-pr-workflows-onboard"] |
Onboard
Overview
This skill turns repository onboarding into an executable, reviewable workflow.
Use it when the operator needs to help a new engineer, contractor, maintainer, or reviewer become productive in an existing repository without guessing hidden setup steps or breaking the established contribution process.
The skill preserves the original intent of the upstream onboarding workflow while improving operational clarity, reproducibility, and handoff quality. It is especially useful when onboarding must retain provenance, copied support files, and upstream workflow expectations during repository intake, migration, or transition.
When to Use
Activate this skill when the request involves one or more of these outcomes:
- getting a new contributor from zero access to a verified local setup
- documenting or reviewing repository onboarding readiness
- checking whether a repo has enough instructions for someone else to contribute safely
- preparing a handoff between maintainers, teams, or vendors
- preserving upstream workflow and provenance while making the onboarding path easier to execute
- identifying missing access, setup, review, or documentation controls before work begins
Do not use this skill as the primary workflow when the task is mainly:
- fixing a single build error with no onboarding or handoff scope
- performing deep architecture analysis unrelated to contributor ramp-up
- writing generic HR onboarding material unrelated to a repository or contribution workflow
- executing privileged access changes that require a separate approval workflow
Operator Focus
| Area | What to confirm | Minimum evidence |
|---|
| Provenance | Upstream source, copied files, and workflow assumptions are preserved | ORIGIN notes, source link, unchanged upstream artifacts where required |
| Access | Required repo, package, secret, CI, and environment access is known | List of required systems and who grants access |
| Reproducibility | A new contributor can set up the environment without tribal knowledge | Documented commands, versions, and expected success signals |
| Contribution path | The contributor knows how to branch, test, commit, and open a PR | CONTRIBUTING path, branch rules, PR expectations |
| Safety | Sensitive credentials and protected workflows are handled correctly |
