bryantleft/bruhs-skills

Overview

This skill is an opinionated development lifecycle plugin that helps teams spawn projects, plan and build features, and ship code with consistent workflows. It provides command-driven actions for project scaffolding, feature work (cook), shipping (yeet), review handling (peep), cleanup (dip), and deep codebase analysis (slop). The tool enforces type-driven design and common engineering rules through configurable project settings.

How this skill works

Invoke via /bruhs to open an interactive menu or call a specific command like /bruhs cook <feature> or /bruhs slop [path] [--fix|--report]. Each command runs a defined workflow: spawn scaffolds projects, cook plans and builds a ticket-scoped feature, yeet turns changes into branch → commit → PR → Linear update, peep addresses review comments, dip cleans up post-merge, and slop runs prioritized codebase analysis with optional auto-fixes. The skill reads and writes configuration in .claude/bruhs.json and integrates with MCPs like Linear and GitHub to automate tickets, branches, and PRs.

When to use it

• Starting a new project or adding a package to a monorepo (spawn).
• Implementing a feature or fixing a ticket end-to-end (cook → yeet).
• Preparing and submitting a clean, standardized PR with linked ticket metadata (yeet).
• Handling reviewer comments and iterating on a PR (peep).
• Cleaning up branches and workspace state after merge (dip).
• Running a deep type-driven codebase audit and auto-fixing safe issues (slop).

Best practices

• Keep .claude/bruhs.json up to date with project stack and MCP settings for full automation.
• Follow the Type-Driven Design checklist: explicit signatures, no any, typed errors, and immutability.
• Use cook to design 2–3 approaches and confirm one before implementing to reduce rework.
• Run slop regularly with severity tuned (relaxed → brutal) to catch type and architecture drift.
• Name branches and commits per the Git rules so automation creates accurate tickets and PRs.

Example use cases

• Scaffold a new Next.js workspace with CI and initial Linear tickets using /bruhs spawn.
• Plan, TDD, and ship a feature linked to TICKET-123: /bruhs cook TICKET-123 then /bruhs yeet.
• Automate addressing PR comments: /bruhs peep to fetch, categorize, and apply fixes interactively.
• Run a targeted static audit of src/components with auto-fixes: /bruhs slop src/components --fix.
• Claim an existing repository and generate .claude/bruhs.json to enable other bruhs commands.