agentsclimarketplace

Repo onboarding standards

Skill chf3198/megingjord-harness/skills/repo-onboarding-standards

AI agent governance harness: baton workflow, fleet LLM routing (Ollama/Claude/OpenRouter), and CI gates for Copilot, Claude Code, and Codex.

Install
npx -y skills add chf3198/megingjord-harness --skill repo-onboarding-standards

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Onboard any repository into a standardized Copilot + CI governance baseline. Use for new repos and first-time sessions to ensure immediate standards adoption.

SKILL.md

2.6 KB, as published. Nobody here has run it

Repo Onboarding Standards

When to use

  • First session in a new repository.
  • Existing repositories lacking standardized AI customization and release/security gates.
  • Requests like: "include all global-skills in your initialization process."

Procedure

  1. Run global-skills-bootstrap in mode=init for repository scaffolding.
  2. Provision canonical label taxonomy: node scripts/global/label-provision.js --repo=<owner/repo>. This seeds all type:*, status:*, priority:*, role:*, area:*, lane:*, resolution:*, and governance labels required for the baton lifecycle. Manifest: scripts/global/label-manifest.json (Refs #2785).
  3. Classify repository type and risk profile using existing routing skills.
  4. Generate baseline repo instructions (.github/copilot-instructions.md) with build/test/gate truth.
  5. Add targeted .github/instructions/*.instructions.md files for stack-specific rules.
  6. Verify CI has minimum baseline: lint/test, dependency/security review, artifact/release checks.
  7. Add or update release policy controls (version integrity, docs sync, packaging audit).
  8. For platforms that support exact-version install/pin, require version-selectability controls:
    • immutable artifact retention,
    • exact-version install smoke checks,
    • canonical version index/source alignment for update prompts,
    • documented rollback and version-yank policy.
  9. Produce an onboarding report with required vs optional controls and evidence.

Required handoffs

  • Run global-skills-bootstrap first for new repositories.
  • Route standards selection via repo-standards-router.
  • Route GitHub workflow governance controls via github-ops-tree-router.
  • Use workflow-self-anneal only post-failure/process mismatch.

Output format

  • repo_classification: type + confidence
  • baseline_status: complete|partial|missing
  • required_controls: must-have controls
  • optional_controls: nice-to-have controls
  • execution_plan: sequenced rollout tasks
  • evidence: files and checks used for conclusions

Standards

  • Prefer smallest correct baseline over over-engineered policy stacks.
  • Require objective verification gates for each recommended control.
  • Do not claim onboarding complete without evidence for every required control.
  • Do not mark release governance complete when an app type can support exact-version installability but lacks enforceable controls for it.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.