preferences

Enforce Git/GitHub conventions for commits, PRs, CI, and Vercel previews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gakonst/dotfiles --skill preferences
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preferences
Source: https://github.com/gakonst/dotfiles/tree/main/.codex/skills/preferences
Command: npx skills add https://github.com/gakonst/dotfiles --skill preferences

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill encapsulates Georgios's default Git/GitHub conventions to keep repos consistent and automation-friendly.

Core Features & Use Cases

  • Conventional commits: standard subject/body; atomic staging.
  • gh-based workflow: use gh for auth, clone, PRs, and API calls.
  • CI gating: path-based filtering to run only affected stacks.

Quick Start

gh auth status; gh repo clone owner/repo ~/github/owner/repo; git add -p; git commit; gh pr checkout <num>.

Frequently Asked Questions about preferences

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

FAQPage Schema
How do I enforce conventional commits in my GitHub workflow?

Conventional commits standardize commit messages with a subject and body format. This Skill enforces that standard across your repository by requiring structured commit messages and atomic staging via `git add -p`, ensuring all changes follow a consistent format that automation tools can parse reliably.

What's the best way to set up Git/GitHub conventions across a team?

This Skill encapsulates default Git/GitHub conventions—conventional commits, gh-based authentication, and CI path-based filtering—to keep repositories consistent. Apply it when cloning repos, making commits, creating PRs, and configuring CI for Rust, Python, TypeScript, and Vercel previews.

How can I use gh for authentication and PR workflows?

The gh CLI handles authentication and repository operations. This Skill uses `gh auth status` to verify credentials, `gh repo clone` for repository setup, and `gh pr checkout` for PR management, centralizing GitHub operations through the gh CLI instead of HTTPS or SSH alternatives.

Can I run CI only for affected code paths in my repository?

CI path-based filtering runs workflows only when specific files or directories change. This Skill uses dorny/paths-filter to gate CI and PR workflows, so Rust, Python, or TypeScript builds trigger only when their respective stack files are modified, reducing unnecessary CI runs.

Does this work with Rust, Python, TypeScript, and Vercel?

Yes. This Skill provides language-specific CI defaults for Rust, Python, and TypeScript, plus configuration for Vercel preview management. It applies conventions consistently across these stacks and their respective CI environments.