# bombfork-setup

> Sets up bombfork projects by validating GitHub remote configuration and creating standardized issue size labels (size-s, size-m, size-l). Use when user asks to setup a project, configure GitHub labels, or initialize project management structure.

- Author: Thomas Nemer
- Repository: bombfork/claude-marketplace
- Version: 20251221150727
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/bombfork/claude-marketplace
- Web: https://mule.run/skillshub/@@bombfork/claude-marketplace~bombfork-setup:20251221150727

---

---
name: bombfork-setup
description: Sets up bombfork projects by validating GitHub remote configuration and creating standardized issue size labels (size-s, size-m, size-l). Use when user asks to setup a project, configure GitHub labels, or initialize project management structure.
---

# Bombfork Project Setup Skill

This skill helps set up bombfork projects with standardized GitHub issue labels.

## When to Use This Skill

Use this skill when the user:
- Asks to "setup the project"
- Wants to configure GitHub issue labels
- Requests project initialization
- Mentions setting up size labels or project management
- Uses the `/setup` command

## What This Skill Does

1. **Validates Git Repository**: Checks that the current directory is a git repository
2. **Checks GitHub Remote**: Ensures a GitHub remote is configured
3. **Creates Issue Labels**: Adds three standardized size labels:
   - `size-s` (green): Issues requiring less than 0.5 days for 1 engineer
   - `size-m` (yellow): Issues requiring less than 1 day for 1 engineer
   - `size-l` (red): Issues requiring more than 1 day for 1 engineer

## Instructions

When this skill is invoked:

1. **Verify Prerequisites**
   - Check if `gh` CLI is installed using `command -v gh`
   - Check if the current directory is a git repository
   - Verify that a GitHub remote exists

2. **Run the Setup Script**
   - Execute the setup script located at: `./src/setup.sh` (relative to this skill's directory)
   - The script will handle all validation and label creation
   - Show the output to the user

3. **Handle Errors Gracefully**
   - If prerequisites are missing, provide clear installation instructions
   - If no GitHub remote exists, guide user to add one
   - If authentication fails, instruct user to run `gh auth login`

## Example Usage

When user says: "Can you run /setup?"

Response:
1. Explain what the setup will do
2. Run the setup.sh script using Bash tool
3. Show the results
4. Provide the GitHub labels URL for verification

## Script Location

The setup script is located at: `[skill-directory]/src/setup.sh`

When invoking, use the absolute path or navigate to the skill directory first.

## Error Handling

Common errors and solutions:

- **Not a git repository**: User needs to run `git init` or navigate to a git repo
- **No GitHub remote**: User needs to add remote with `git remote add origin <url>`
- **gh not installed**: User needs to install from https://cli.github.com/
- **Not authenticated**: User needs to run `gh auth login`
- **No write access**: User needs proper permissions on the repository

## Reference Files

- `reference.md` - Additional documentation
- `examples/usage-example.md` - Detailed usage examples
- `src/setup.sh` - The actual setup script