onboard

Name: onboard
Availability: InStock
Author: kagenti

Clone a repository into `.repos/` and apply Kagenti conventions.

292|103|Updated Mar 27, 2025

Search Tags:#workflow #devops #onboarding #integration #repository management #kagenti

Ready to run

npx skills add https://github.com/kagenti/kagenti --skill onboard-kagenti

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/onboard
Command: npx skills add https://github.com/kagenti/kagenti --skill onboard-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating a new or existing repository into the Kagenti ecosystem, ensuring it adheres to project standards and is discoverable within the hub.

Core Features & Use Cases

Repository Integration: Clones and configures external repositories to work seamlessly with Kagenti.
Standardization: Applies Kagenti's conventions for commit messages, pull requests, and issue tracking.
Discovery: Registers the onboarded repository in the Kagenti hub inventory for easy access and management.
Use Case: A new project lead needs to add their team's codebase to the central Kagenti platform. They use the onboard skill to clone the repo, apply the required Kagenti templates, and make it visible to other teams.

Quick Start

Run the onboard skill to connect the current repository to the Kagenti hub.

Frequently Asked Questions about onboard

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

FAQPage Schema

How do I integrate an external repository into the Kagenti hub?▼

To integrate a repository into the Kagenti hub, run the onboard skill to clone it into the local `.repos/` directory and apply Kagenti-specific conventions for standardized management.

What prerequisites are needed to connect a repository to the Kagenti hub?▼

Before connecting a repository to the Kagenti hub, the target repository must complete the prerequisite `orchestrate:scan` and `orchestrate:precommit` steps to ensure compliance with project standards.

How does repository onboarding apply project conventions for DevOps workflows?▼

Repository onboarding applies Kagenti conventions by automatically configuring commit messages, pull requests, and issue tracking templates to standardize your DevOps workflow and project integration.

Can I use the onboard skill to make an existing codebase discoverable in the Kagenti hub?▼

Yes, you can use the onboard skill to register an existing codebase in the Kagenti hub inventory, making it visible and easily accessible for other teams to manage.

What is the best way to clone and configure external repositories for Kagenti?▼

The best way to clone and configure external repositories is using the onboard skill, which links the repository to the Kagenti hub and applies required templates seamlessly for project leads.

Why does repository onboarding fail if orchestrate scan and precommit steps are missing?▼

Repository onboarding fails without `orchestrate:scan` and `orchestrate:precommit` steps because the Kagenti hub requires these prerequisite checks to ensure the repository meets all integration standards before linking.