Skill: Homebrew Distribution
openbooklet.com/s/skill-homebrew-distributionopenbooklet.com/s/skill-homebrew-distribution@1.0.0GET /api/v1/skills/skill-homebrew-distribution**Name**: homebrew **Description**: Homebrew formula management and macOS/Linux distribution **Trigger**: "Homebrew release", brew installation, macOS/Linux distribution
**Objective**: Fix the `update-formula.sh` script in `BA-CalderonMorales/homebrew-terminal-jarvis` to prevent deployment failures.
**Name**: code-quality **Description**: Code quality gates, formatting, and best practices **Trigger**: All code changes, before commits, code review
**Name**: refactoring **Description**: Domain-based module extraction and code organization **Trigger**: "Refactor this file", large files (>200 lines), code organization
**Name**: git-workflow **Description**: Branching strategy, merge rules, and git best practices **Trigger**: All git operations, branching, merging, commits
**Name**: multi-repo **Description**: Cross-repository documentation synchronization pattern for projects with separate code and docs repos **Trigger**: "Sync docs across repos", "Cross-repo version sync", "Update external docs", "Multi-repo release"
**Name**: qa-testing **Description**: Create and manage minimal QA test branches for release verification **Trigger**: "Test this release", "Create QA branch", "Verify in fresh Codespace", "QA for v0.0.X"
**Name**: release **Description**: Complete agent-driven release process with cross-repo docs synchronization **Trigger**: "Release v0.0.X", "Cut new release", "Publish release with docs sync", "Agent release"
**Name**: testing **Description**: Test-driven bugfixes and testing practices **Trigger**: "Fix this bug", bug fixes, new features requiring tests
**Name**: token-budget **Description**: Token efficiency patterns for long AI coding sessions **Trigger**: Long sessions, complex multi-step tasks, session optimization
**Name**: tool-launch-verification **Description**: Session-based verification of all Terminal Jarvis command paths for tool operations and runtime flow integrity **Trigger**: "verify tool launches", "which tools are actually operational", pre-release launch validation
**Name**: verification **Description**: Quality verification system for validating changes before commits **Trigger**: Before commits, after code changes, bug fixes, UX changes
**Name**: versioning **Description**: Semantic versioning and multi-platform version synchronization **Trigger**: "Update version", version bumps, release preparation
**A guide to diagnosing and fixing complex deployment failures in the Terminal Jarvis ecosystem.**
Auto-indexed from BA-CalderonMorales/terminal-jarvis
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.