Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Onboard:Standards

ASecurity

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

302 stars
0 votes
0 copies
0 views
Added 9/20/2026
devopsbashkubernetesrefactoringgitci/cddocumentation

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$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 automatically 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.

Download Zip
Files
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

rossoctlrossoctl
View sourceMore from rossoctl →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

393431 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2459130 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

929660 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

805540 votes
View all in devops →