shellicar-config-conventions

Enforce no-PR Git conventions for personal configuration repositories.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/shellicar/claude-config --skill shellicar-config-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shellicar-config-conventions
Source: https://github.com/shellicar/claude-config/tree/main/skills/shellicar-config-conventions
Command: npx skills add https://github.com/shellicar/claude-config --skill shellicar-config-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git conventions for personal configuration repositories without PRs.

Core Features & Use Cases

  • Direct commits to main in personal dotfiles/projects.
  • Simple, deterministic workflow with minimal branching.
  • Use Case: when you want a private config repo to stay clean and quick.

Quick Start

Initialize a config repo to follow the no-PR workflow by committing directly to main after changes.

Frequently Asked Questions about shellicar-config-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage git conventions for personal config repos without pull requests?

Git conventions for personal configuration repos enforce a no-PR workflow by guiding direct commits to main. This suits dotfiles workflows and home configuration spaces, keeping private repos clean and quick with minimal branching.

What is the best way to commit dotfiles directly to main?

The best way to commit dotfiles directly to main is using a no-PR git convention. This approach enforces direct commits and minimal branching, providing a deterministic workflow for personal configuration repositories.

Do I need a SKILL.md file to set up config repo conventions?

Yes, you need a SKILL.md file at the repo root to set up these config repo conventions. It must include YAML frontmatter declaring the name and description. Optional scripts, references, and assets directories may be included.

When should I use a no-PR git workflow for personal repositories?

Use a no-PR git workflow for personal repositories when you want a private config repo to stay clean and quick. It is designed for home configuration spaces and dotfiles workflows requiring simple, deterministic management with minimal branching.

Can I use branching with personal dotfiles repos following no-PR conventions?

Branching is kept minimal with these personal dotfiles conventions. The no-PR workflow targets direct commits to main for simple, deterministic management, ensuring personal configuration repositories stay clean without complex branching strategies.