README

A README guide to Git workflow and quality-check commands for the Claude Skills repository. Git is a tool for tracking code changes, while quality checks look for errors before sharing them.

In plain words
What is it for?
Use it as a quick reference for the repository's commands, including local commits, publishing branches, GitHub pull requests, branch cleanup, reviews, and documentation updates.
Why use it?
It explains which command to use for committing, pushing, opening pull requests, cleaning branches, reviewing code, and scanning for security problems.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/alirezarezvani/claude-skills/readme
Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,825 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01825
Opus 5 $0.00000 $0.00912
Sonnet 5 $0.00000 $0.00365
Haiku 4.5 $0.00000 $0.00183

Measured yesterday against content hash 778f4b834409, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

README scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • README — 100% identical, 0 lines differ
  • README — 100% identical, 0 lines differ
.claude/commands/README.md · 352 lines

How it starts

The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Skills Slash Commands

Git workflow and quality assurance commands for the claude-skills repository.


🎯 Essential Commands

Git Workflow

/git:cm         → Stage and commit (no push)
/git:cp         → Stage, commit, and push
/git:pr         → Create pull request
/git:clean      → Delete merged branches (local + remote)

Quality Gates

/review         → Run local quality checks
/security-scan  → Run security validation
/update-docs    → Post-creation sync (CLI platforms, marketplace, docs, GitHub Pages)

📋 Git Commands

/git:cm - Commit (No Push)

Purpose: Stage changes and create a conventional commit without pushing

Usage:

/git:cm

What it does:

  1. Shows git status --short
  2. Reviews each file diff for secrets
  3. Stages files intentionally
  4. Generates conventional commit message
  5. Creates commit (no push)

When to use: When you want to commit locally before pushing


/git:cp - Commit and Push

Purpose: Complete git workflow with quality checks

Usage:

/git:cp

What it does:

  1. Runs /review for quality checks
  2. Stages changes
  3. Creates conventional commit
  4. Pushes to origin
  5. Triggers CI workflows

When to use: When ready to publish changes


/git:pr - Create Pull Request

Purpose: Create a PR from current branch

Usage:

/git:pr              # PR to main
/git:pr dev          # PR to dev branch

What it does:

  1. Verifies quality checks passed
  2. Creates PR using template
  3. Adds appropriate labels
  4. Shares PR link

When to use: After pushing changes and ready for review


🔒 Quality Commands

/review - Local Quality Gate

Purpose: Run all quality checks before pushing

Usage:

/review

What it checks:

  • ✅ YAML linting (workflows)
  • ✅ GitHub workflow schema validation
  • ✅ Python syntax (all skill directories)
  • ✅ Markdown link validation
  • ✅ Dependency security audit (optional)

When to use: Before committing/pushing changes

Read the full file on GitHub · 352 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 352 lines · 0 tokens per session scan A 778f4b834409

Subscribe to this mod's changes

README is a command published in the GitHub repository alirezarezvani/claude-skills (25,247 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,825 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.