# Shell

> Bring a repo to the SHELL house standard: tiers, Apache-2.0 license files, GitHub metadata, README identity, secret scanning, and a compliance report. Use when the user says shell check, standardize this repo, make repos compliant, audit my repos, or bring this repo to house standard.

- Skill: `hongyime/shell` (Agent Skill)
- Install (CLI): `npx get-skill add hongyime/shell`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hongyime/shell/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: hongyime (https://skillmd.com/u/hongyime)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/hongyime/shell

---


# SHELL — the house standard for repos

Alias for `repo-standardization`. SHELL is the desired state every repo
must meet: correct tier-appropriate files, metadata, licensing, and
hygiene — then prove it with a compliance report. SHELL here is the house
standard, not a terminal shell.

## When to use it

- The user says shell check, standardize this repo, make repos compliant,
  audit my repos, scaffold a new repo, or bring this repo to house
  standard.

## How it works

Load `repo-standardization` and follow it. It covers repo tiers,
Apache-2.0 LICENSE and NOTICE files, GitHub description/homepage/topics
metadata, README identity block, secret/identity scanning, compliance
reports, and new-repo scaffolding.

## Provenance

Adapted from the SHELL standard (STANDARD.md + tiers + repo inventory).
The standard's former home, hongyime/sourcerepo/STANDARD.md, was retired
from sourcerepo on 2026-11-14. The standard now lives in the
`repo-standardization` skill — its checklist is the standard. The `_shell/`
folder holds a local copy of the retired document. This skill is the
library's alias for it.

