meta--onboarding

Coordinate repository onboarding with read-only audits and centralized evidence tracking.

57|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/patterninc/code-mint --skill meta-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta--onboarding
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/meta--onboarding
Command: npx skills add https://github.com/patterninc/code-mint --skill meta-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The onboarding playbook transforms a bare repository into an AI-first environment with auditable proofs and clear progress tracking.

Core Features & Use Cases

  • Phase-based onboarding with discovery, audits, and evidence-based progress
  • Outcome-driven checkpoints and centralized documentation in repo
  • Collaboration and approvals that gate remediation with traceability

Quick Start

Run the onboarding playbook against your repository and follow the phase prompts to collect evidence and track progress.

Frequently Asked Questions about meta--onboarding

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

FAQPage Schema
What is repository onboarding for AI-first development?

Repository onboarding transforms a bare repository into an AI-first environment by running read-only audits, tracking outcomes in a centralized checklist, and storing auditable proofs inside the repo for repeatable activation.

How do I audit a repository for AI-first development readiness?

You audit a repository by running an assessment-first playbook that scopes the codebase, executes read-only audits, and records auditable proofs and evidence in a centralized checklist within the repo.

Can I track repository onboarding progress with evidence and checkpoints?

Yes, the onboarding playbook uses phase-based discovery with outcome-driven checkpoints, tracking all audit results and evidence centrally inside the repository for clear progress visibility.

Does repository onboarding require explicit approvals for remediation steps?

Yes, the onboarding process gates collaborative remediation with explicit approvals to ensure traceability and requires risky steps to be authorized before proceeding with repository activation.

What's the best way to manage governance and compliance during repository onboarding?

The best way to manage governance during onboarding is using an assessment-first playbook that runs read-only audits, stores evidence inside the repository, and tracks compliance outcomes in a centralized checklist.

Why do I need to store onboarding evidence and audit results inside the repository?

Storing audit results and evidence inside the repository ensures repeatable activation, maintains auditable proofs for governance, and provides centralized documentation for collaborative remediation tracking.