Skip to content
Back to skills

Onboard:Standards

ASecurity

Apply rossoctl-specific conventions to an onboarded repo - commit format, PR template, issue templates

  • 299 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 20, 2026
devopsbashkubernetesrefactoringgitci/cddocumentation

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add rossoctl/rossoctl --skill onboard:standards --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Onboard:Standards?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Onboard:Standards
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/rossoctl-onboard-standards/badge)](https://www.skillsdirectory.com/skills/rossoctl-onboard-standards)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: onboard:standards
description: Apply rossoctl-specific conventions to an onboarded repo - commit format, PR template, issue templates
---

# Onboard: Apply Rossoctl Standards

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

## Conventions

### 1. Commit message format

Rossoctl uses emoji prefixes and sign-off:

| Emoji | Type | Usage |
|-------|------|-------|
| ✨ | feat | New feature |
| πŸ› | fix | Bug fix |
| πŸ“ | docs | Documentation |
| πŸ”§ | config | Configuration |
| ⬆️ | deps | Dependency update |
| ♻️ | refactor | Refactoring |
| βœ… | test | Tests |
| πŸ‘· | ci | CI/CD changes |

Sign-off required: `git commit -s`

### 2. PR template

Create `.github/pull_request_template.md`:

```markdown
## 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`:

```markdown
---
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`:

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

## Problem Statement

## Proposed Solution

## Alternatives Considered
```

### 4. Branch naming

| Prefix | Usage |
|--------|-------|
| `feat/` | New features |
| `fix/` | Bug fixes |
| `docs/` | Documentation |
| `orchestrate/` | Orchestration changes |

## Workflow

### Step 1: Create branch

```bash
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

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

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

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

### Step 4: Create PR

```bash
gh pr create --repo org/repo --title "Add rossoctl project conventions" --body "Applies rossoctl 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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.