onboardstandards

name: onboard:standards description: Apply kagenti-specific conventions to an onboarded repo - commit format, PR template, issue templates

Onboard: Apply Kagenti Standards

Apply kagenti-specific conventions to a repository linked via onboard:link.

Conventions

1. Commit message format

Kagenti uses emoji prefixes and sign-off:

Sign-off required: git commit -s

2. PR template

Create .github/pull_request_template.md:

## Summary
<!-- What does this PR do? Why? -->

## Test Plan
- [ ] Unit tests pass
- [ ] E2E tests pass (if applicable)
- [ ] Manual verification documented below

## Additional Context
<!-- Link issues, screenshots, etc. -->

3. Issue templates

Create .github/ISSUE_TEMPLATE/bug_report.md:

---
name: Bug Report
about: Report a bug
labels: bug
---

## Describe the Bug

## Steps to Reproduce
1.
2.

## Expected Behavior

## Actual Behavior

## Environment
- Kubernetes version:
- Cluster type:

Create .github/ISSUE_TEMPLATE/feature_request.md:

---
name: Feature Request
about: Suggest an enhancement
labels: enhancement
---

## Problem Statement

## Proposed Solution

## Alternatives Considered

4. Branch naming

Workflow

Step 1: Create branch

git -C .repos/<repo-name> checkout -b orchestrate/onboard-standards

Step 2: Apply conventions

Create or update the files above. Skip any that already match.

Step 3: Commit and push

git -C .repos/<repo-name> add .github/

git -C .repos/<repo-name> commit -s -m "✨ Add kagenti PR and issue templates"

git -C .repos/<repo-name> push -u origin orchestrate/onboard-standards

Step 4: Create PR

gh pr create --repo org/repo --title "Add kagenti project conventions" --body "Applies kagenti standards: commit format, PR template, issue templates, branch naming."

Step 5: Update inventory

Set status to Onboarded in .repos/README.md.

Related Skills

• onboard — Router skill
• onboard:link — Clone and register (prerequisite)
• orchestrate:precommit — Pre-commit hooks (complementary)