RUNWAY
<img src="https://raw.githubusercontent.com/unparty-app/unparty-app.github.io/main/logo-theunpartyapp.svg" width="18" alt="Logo">
<img src="https://raw.githubusercontent.com/unparty-app/unparty-app.github.io/main/building-icon.svg" width="18" alt="Building">
THEUNPARTYRUNWAY is building jobs, not dependencies.
YOU DREAM. AI HALLUCINATES. INNOVATE THE DIFFERENCE.
ABOUT theunpartyrunway
-
đ THOUGHT
Generative AI models can be incredibly useful for learning about problems we once thought were impossible to solve. -
đ RISK
Without grounding generative AI models in reality, we risk building thoughts instead of solutions. -
â CHALLENGE
Can we build a foundational model that connects impossible problems to possible solutions by learning from:- what already exists
- what we want to exist
- what it takes to make it exist
GATEKEEPERS
theunpartyrunway HAS 5ī¸âŖ GATEKEEPERS
- BRAND
- CORE
- BUDGET
- PRODUCT
- RISK
- GROW
YOU'LL FIT IN IF:
- YOU ARE IN A BUILD STAGE
- YOU THINK STAYING ORGANIZED IS KEY.
YOU'LL HATE IT HERE IF:
- YOU HATE CODE
đĒŠ PARTIES:
automated semantic branching system designed for solo developers to maintain clean, organized development workflows without manual overhead.
đ Quick Start
1. Create a New Feature Branch
bash
# Smart branch creation with auto-naming and issue generation
./scripts/smart-branch.sh <directory> [description]
# Examples:
./scripts/smart-branch.sh data "claude-cost-analysis"
./scripts/smart-branch.sh dashboard "user-metrics"
./scripts/smart-branch.sh docs "api-reference"2. Work on Your Changes
The system automatically:
- â
Creates semantic branch names (
feature/data-claude-cost-analysis-20250606) - â Sets up commit message templates for your branch context
- â Generates GitHub issues with appropriate templates
- â Configures branch for immediate productivity
3. Commit Your Work
bash
# Use the pre-configured commit template
git commit -t .git/BRANCH_COMMIT_TEMPLATE
# Or manually follow semantic commit format:
git commit -m "data(claude-costs): improve analysis accuracy"4. Create Pull Request
bash
# Create PR with auto-generated templates
gh pr create --title "Feature: Your Description" --body "Brief description"
# The PR template adapts based on which directories you've changedđ Directory-Based Automation
Our system automatically detects changes and creates appropriate workflows:
| Directory | Branch Type | Commit Type | Auto-Generated Issue |
|---|---|---|---|
data/, expenses/, revenue/ | data | data | Data validation checklist |
docs/, README.md | docs | docs | Documentation review tasks |
scripts/, analysis files | feature | analysis | Code review checklist |
.github/, config files | config | ci | Configuration validation |
| Other directories | feature | feat | General feature template |
đ ī¸ Available Tools
Smart Branch Creation
./scripts/smart-branch.sh- Intelligent branch creation with auto-naming- Features: Auto-detects branch type, creates issues, sets up templates
Data Management
./scripts/auto_claude_data_processor.py- Auto-discovers and validates all data files./scripts/add_new_claude_data.sh- Drag-drop workflow for new data files./scripts/cleanup_data_directory.py- Consolidate and organize data files
Analysis Tools
./scripts/claude_data_dependency_analyzer.py- Analyzes data usage across codebase./scripts/development_velocity_analyzer.py- Claude usage pattern analysis./scripts/claude_git_correlation_analyzer.py- Git activity correlation
đ¯ Workflow Examples
Example 1: Adding New Data Analysis
bash
# 1. Create branch for data work
./scripts/smart-branch.sh data "monthly-revenue-analysis"
# 2. Add your data files (auto-detected and validated)
./scripts/add_new_claude_data.sh path/to/new_data.csv
# 3. Work on analysis scripts
# 4. Commit with context-aware template
git commit -t .git/BRANCH_COMMIT_TEMPLATE
# 5. Push and create PR
git push
gh pr create --title "Data Analysis: Monthly Revenue Insights"Example 2: Documentation Updates
bash
# 1. Create docs branch
./scripts/smart-branch.sh docs "api-documentation-update"
# 2. Update documentation files
# 3. Commit with semantic message
git commit -m "docs(api): update endpoint documentation"
# 4. Auto-generated PR template includes docs checklist
gh pr createExample 3: Feature Development
bash
# 1. Create feature branch
./scripts/smart-branch.sh dashboard "real-time-metrics"
# 2. GitHub issue automatically created with feature template
# 3. Develop your feature
# 4. Commit following semantic conventions
git commit -m "feat(dashboard): add real-time metrics display"
# 5. PR includes feature testing checklistđ GitHub Integration
Automated Issue Creation
- Triggers: When using
smart-branch.shor GitHub Actions workflows - Templates: Automatically selected based on directory/change type
- Labels: Auto-applied for easy filtering and organization
Pull Request Templates
- Adaptive: Changes based on which directories are modified
- Checklists: Context-specific validation steps
- Integration: Links to related issues automatically
GitHub Actions Workflows
- Semantic Branching:
.github/workflows/semantic-branching.yml - Auto-detects changed directories and suggests branch names
- Creates issues for manual workflow dispatch
- Validates semantic commit conventions
đ§ Configuration
Commit Message Template
Located at .gitmessage - provides semantic commit guidance:
Code
# <type>(<scope>): <subject>
# Types: feat, fix, docs, style, refactor, test, chore, data, analysis, config, ci
# Scope: archive, assumptions, cache, calendar, dashboard, data, docs, etc.Branch Protection
The system prevents direct commits to main and encourages:
- Feature branch development
- Pull request reviews
- Semantic commit messages
- Automated testing and validation
đ Data Management
Master Data Files
data/claude_api_cost_master.csv- Consolidated cost datadata/claude_api_tokens_master.csv- Consolidated token usage- Auto-validated and deduplicated during consolidation
Data Quality
- Automated validation on all data changes
- Dependency analysis ensures complete data coverage
- Gap detection and automatic template generation
đ Benefits
For Solo Development
- Reduced cognitive overhead - automation handles workflow decisions
- Consistent practices - semantic conventions enforced automatically
- Issue tracking - automatic organization and templates
- Clean history - semantic commits and organized branches
For Code Quality
- Automated validation - data quality checks and code analysis
- Dependency tracking - comprehensive codebase analysis
- Change detection - intelligent workflow triggering
- Documentation - automatically updated and validated
đ Additional Resources
- Issue Templates:
.github/ISSUE_TEMPLATE/ - PR Template:
.github/PULL_REQUEST_TEMPLATE.md - Data Documentation:
data/README.md - Script Documentation:
scripts/README.md
<img src="https://raw.githubusercontent.com/unparty-app/unparty-app.github.io/main/talking-icon.svg" width="18" alt="Thinking"> | <img src="https://raw.githubusercontent.com/unparty-app/unparty-app.github.io/main/building-icon.svg" width="18" alt="Building">
| <img src="https://raw.githubusercontent.com/unparty-app/unparty-app.github.io/main/growing-icon.svg" width="18" alt="Growing">
đ¤ This workflow system is designed to maximize development velocity while maintaining high code quality and organization standards.