skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

onboard:standards

Apply Kagenti development conventions to a linked repository.

292|103|Updated Mar 27, 2025
Search Tags:#git#workflow#templates#onboarding#github#convention
One-click install
npx skills add https://github.com/kagenti/kagenti --skill onboard-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard:standards
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/onboard%3Astandards
Command: npx skills add https://github.com/kagenti/kagenti --skill onboard-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the application of Kagenti's specific development conventions to a repository, ensuring consistency in commit messages, pull request templates, and issue templates.

Core Features & Use Cases

  • Commit Convention Enforcement: Implements emoji prefixes for commit types (feat, fix, docs, etc.) and requires a sign-off.
  • Standardized Templates: Creates or updates .github/pull_request_template.md, .github/ISSUE_TEMPLATE/bug_report.md, and .github/ISSUE_TEMPLATE/feature_request.md.
  • Branch Naming Guidelines: Enforces prefixes like feat/, fix/, docs/, orchestrate/.
  • Use Case: When onboarding a new repository into the Kagenti ecosystem, this skill ensures it adheres to the established development workflow and best practices, improving collaboration and maintainability.

Quick Start

Apply kagenti-specific conventions to an onboarded repo by running the onboard:standards skill.

Frequently Asked Questions about onboard:standards

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

FAQPage Schema
How do I standardize git commit conventions and PR templates across my repository?▼

To standardize git conventions, you can apply automated templates that enforce emoji prefixes for commit types, require sign-offs, and generate standardized pull request and issue templates for your repository.

What is the best way to enforce branch naming conventions like feat/ and fix/ in GitHub?▼

Enforcing branch naming conventions involves applying standardized prefixes such as feat/, fix/, and docs/ to your workflow, ensuring repository branches adhere to established project standards for consistency.

Do I need GitHub CLI to automate pull request and issue template creation?▼

Yes, GitHub CLI is required alongside git to automate the creation and enforcement of repository conventions, including generating pull request templates and issue templates in your repository.

Can I automatically add bug report and feature request issue templates to a GitHub repo?▼

Yes, you can automatically create or update .github/ISSUE_TEMPLATE/bug_report.md and feature_request.md files, ensuring your repository has standardized issue reporting formats for better collaboration.

How do I ensure new repositories follow existing project standards during onboarding?▼

To ensure new repositories follow project standards during onboarding, apply automated development conventions that enforce commit message formats, branch naming guidelines, and standardized PR and issue templates.

What commit message format requires emoji prefixes and a sign-off?▼

A commit message format with emoji prefixes categorizes commits by type like feat, fix, or docs, and requires a sign-off to ensure traceability and adherence to established development conventions.

Related Skills

Explore More Software Engineering Skills→
zachmayerzachmayer
2

private-repo

Automates initialization and remote sync of local directories to private GitHub repositories.

Community
Intermediate
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
ongspxmongspxm
1

setup-precommit

Set up pre-commit hooks and generate .pre-commit-config.yaml for Python, shell, and web files.

Community
Intermediate
btabaskabtabaska
1

rule-github-issues

Validate GitHub issue, PR, and workflow templates against repository conventions.

Community
Advanced