vibe-forge 0.4.0 → 0.8.1

package/.claude/commands/clear-attention.md

@@ -1,63 +1,63 @@
----
-description: Clear an attention signal after helping a worker
-argument-hint: [agent-name | all]
----
-
-# Clear Attention Command
-
-Use this command to clear attention signals after you've helped a blocked worker.
-
-## Usage
-
-```
-/clear-attention anvil    # Clear Anvil's attention signal
-/clear-attention all      # Clear all attention signals
-/clear-attention          # List current attention signals
-```
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-### If no argument or empty
-
-List all current attention signals from `tasks/attention/`:
-
-```
-🔔 Current Attention Signals:
-
-1. Anvil (5 min ago): Need clarification on auth implementation
-2. Crucible (2 min ago): Tests failing, unsure of expected behavior
-
-Use /clear-attention <agent> to resolve.
-```
-
-### If argument is "all"
-
-Remove all files from `tasks/attention/` and confirm:
-
-```
-✅ Cleared all attention signals (2 resolved)
-```
-
-### If argument is an agent name
-
-1. Find and remove files matching that agent in `tasks/attention/`
-2. Confirm removal:
-
-```
-✅ Cleared attention signal for Anvil
-```
-
-If no matching signal found:
-
-```
-No attention signal found for Anvil
-```
-
-## Notes
-
-- Attention files are created by workers using `/need-help`
-- The daemon watches this folder and sends notifications
-- Clearing signals is a way to acknowledge you've responded
-- Workers can also clear their own signals when unblocked
+---
+description: Clear an attention signal after helping a worker
+argument-hint: [agent-name | all]
+---
+
+# Clear Attention Command
+
+Use this command to clear attention signals after you've helped a blocked worker.
+
+## Usage
+
+```
+/clear-attention anvil    # Clear Anvil's attention signal
+/clear-attention all      # Clear all attention signals
+/clear-attention          # List current attention signals
+```
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+### If no argument or empty
+
+List all current attention signals from `tasks/attention/`:
+
+```
+🔔 Current Attention Signals:
+
+1. Anvil (5 min ago): Need clarification on auth implementation
+2. Crucible (2 min ago): Tests failing, unsure of expected behavior
+
+Use /clear-attention <agent> to resolve.
+```
+
+### If argument is "all"
+
+Remove all files from `tasks/attention/` and confirm:
+
+```
+✅ Cleared all attention signals (2 resolved)
+```
+
+### If argument is an agent name
+
+1. Find and remove files matching that agent in `tasks/attention/`
+2. Confirm removal:
+
+```
+✅ Cleared attention signal for Anvil
+```
+
+If no matching signal found:
+
+```
+No attention signal found for Anvil
+```
+
+## Notes
+
+- Attention files are created by workers using `/need-help`
+- The daemon watches this folder and sends notifications
+- Clearing signals is a way to acknowledge you've responded
+- Workers can also clear their own signals when unblocked

package/.claude/commands/compact-context.md

@@ -0,0 +1,52 @@
+# Compact Context
+
+Compress the current conversation to free up context window space while preserving all essential information.
+
+## When to Use
+
+Use this when:
+- You notice response quality degrading (repetitive, forgetting earlier decisions)
+- A task is running long and you want to continue without starting fresh
+- The conversation history is getting unwieldy
+- Before picking up a new task in the same session
+
+## How to Compact
+
+Summarize the current conversation into a dense brief using this format:
+
+```
+## Context Compact — [timestamp]
+
+### Work In Progress
+- Task: [task ID and title]
+- Status: [what's done, what's not]
+- Files touched: [list]
+
+### Key Decisions Made
+- [decision 1 and the reason behind it]
+- [decision 2 and the reason behind it]
+
+### Architecture Constraints Discovered
+- [any patterns, restrictions, or conventions learned from reading code]
+
+### Tests Written
+- [test file: X tests passing]
+
+### Blockers / Open Questions
+- [anything unresolved]
+
+### Next Step
+[Exactly what to do next when work resumes]
+```
+
+After writing the summary, respond with:
+
+> Context compacted. Summary above replaces prior conversation history.
+> Ready to continue with: [next step].
+
+## Rules
+
+- Never lose acceptance criteria state -- list any unchecked ACs explicitly
+- Never lose test counts -- the DoD requires accurate numbers
+- Keep the summary under 400 words -- longer defeats the purpose
+- If mid-task: the summary IS the handoff. Make it complete enough to resume cold.

package/.claude/commands/configure-vcs.md

@@ -1,102 +1,102 @@
----
-description: Configure or re-detect version control system settings
-argument-hint: [detect|set <type>]
----
-
-# Configure VCS Command
-
-Configure or re-detect the version control system for this project. This affects how agents handle branching, PRs, and CI workflows.
-
-## Usage
-
-```
-/configure-vcs                  # Interactive configuration
-/configure-vcs detect           # Auto-detect from project structure
-/configure-vcs set github       # Manually set to GitHub
-/configure-vcs set gitlab       # Manually set to GitLab
-/configure-vcs set gitea        # Manually set to Gitea (self-hosted)
-/configure-vcs set azure-devops # Manually set to Azure DevOps
-/configure-vcs set bitbucket    # Manually set to Bitbucket
-/configure-vcs set git-only     # Git without platform
-/configure-vcs set none         # No version control
-```
-
-## Supported Platforms
-
-| Type | Platform | PR Command | CI Config |
-|------|----------|------------|-----------|
-| `github` | GitHub | `gh pr create` | `.github/workflows/` |
-| `gitlab` | GitLab | `git push -o merge_request.create` | `.gitlab-ci.yml` |
-| `gitea` | Gitea/Codeberg | `tea pr create` | `.gitea/workflows/` |
-| `azure-devops` | Azure DevOps | `az repos pr create` | `azure-pipelines.yml` |
-| `bitbucket` | Bitbucket | Manual via UI | `bitbucket-pipelines.yml` |
-| `git-only` | Git (no platform) | N/A | N/A |
-| `none` | No VCS | N/A | N/A |
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-### If no arguments (interactive mode):
-
-1. Run detection: `node bin/lib/vcs.js detect`
-2. Show current setting and detected type
-3. Ask user to confirm or change
-4. Run `node bin/lib/vcs.js init <type>` to create folders
-5. Report configuration saved
-
-### If `detect`:
-
-1. Run: `node bin/lib/vcs.js detect`
-2. Display detected type and confidence
-3. If confident detection, ask to apply
-4. Run `node bin/lib/vcs.js set <type>` to save
-
-### If `set <type>`:
-
-1. Validate type is one of: github, gitlab, azure-devops, bitbucket, git-only, none
-2. Run: `node bin/lib/vcs.js init <type>`
-3. Report folders created (if any)
-4. Confirm configuration saved
-
-## Detection Logic
-
-The VCS detector checks (in order of priority):
-
-1. **Platform folders**: `.github/`, `.gitlab/`, `.gitea/`, `.azure/`
-2. **CI config files**: `.gitlab-ci.yml`, `azure-pipelines.yml`, `bitbucket-pipelines.yml`
-3. **Git remote URL**: Parses `.git/config` for github.com, gitlab.com, gitea, codeberg.org, etc.
-4. **Fallback**: `git-only` if `.git/` exists, `none` otherwise
-
-## Impact on Agents
-
-When VCS is configured, agents will:
-
-- **github**: Use `gh pr create`, reference GitHub Actions
-- **gitlab**: Use merge request workflow, reference GitLab CI
-- **azure-devops**: Use `az repos pr create`, reference Azure Pipelines
-- **bitbucket**: Provide manual PR instructions, reference Bitbucket Pipelines
-- **git-only**: Use branch workflow without PR commands
-- **none**: Skip all git-related instructions
-
-## Configuration File
-
-VCS config is stored in `.forge/config.json`:
-
-```json
-{
-  "vcs": {
-    "type": "github",
-    "name": "GitHub",
-    "autoDetected": false,
-    "lastUpdated": "2026-01-16T12:00:00Z"
-  }
-}
-```
-
-## When to Use
-
-- **Initial setup**: Automatically run during `forge init`
-- **Adding git later**: Run `/configure-vcs detect` after `git init`
-- **Switching platforms**: Run `/configure-vcs set <type>` when migrating
-- **Troubleshooting**: Run `/configure-vcs` if agents give wrong git instructions
+---
+description: Configure or re-detect version control system settings
+argument-hint: [detect|set <type>]
+---
+
+# Configure VCS Command
+
+Configure or re-detect the version control system for this project. This affects how agents handle branching, PRs, and CI workflows.
+
+## Usage
+
+```
+/configure-vcs                  # Interactive configuration
+/configure-vcs detect           # Auto-detect from project structure
+/configure-vcs set github       # Manually set to GitHub
+/configure-vcs set gitlab       # Manually set to GitLab
+/configure-vcs set gitea        # Manually set to Gitea (self-hosted)
+/configure-vcs set azure-devops # Manually set to Azure DevOps
+/configure-vcs set bitbucket    # Manually set to Bitbucket
+/configure-vcs set git-only     # Git without platform
+/configure-vcs set none         # No version control
+```
+
+## Supported Platforms
+
+| Type | Platform | PR Command | CI Config |
+|------|----------|------------|-----------|
+| `github` | GitHub | `gh pr create` | `.github/workflows/` |
+| `gitlab` | GitLab | `git push -o merge_request.create` | `.gitlab-ci.yml` |
+| `gitea` | Gitea/Codeberg | `tea pr create` | `.gitea/workflows/` |
+| `azure-devops` | Azure DevOps | `az repos pr create` | `azure-pipelines.yml` |
+| `bitbucket` | Bitbucket | Manual via UI | `bitbucket-pipelines.yml` |
+| `git-only` | Git (no platform) | N/A | N/A |
+| `none` | No VCS | N/A | N/A |
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+### If no arguments (interactive mode):
+
+1. Run detection: `node bin/lib/vcs.js detect`
+2. Show current setting and detected type
+3. Ask user to confirm or change
+4. Run `node bin/lib/vcs.js init <type>` to create folders
+5. Report configuration saved
+
+### If `detect`:
+
+1. Run: `node bin/lib/vcs.js detect`
+2. Display detected type and confidence
+3. If confident detection, ask to apply
+4. Run `node bin/lib/vcs.js set <type>` to save
+
+### If `set <type>`:
+
+1. Validate type is one of: github, gitlab, azure-devops, bitbucket, git-only, none
+2. Run: `node bin/lib/vcs.js init <type>`
+3. Report folders created (if any)
+4. Confirm configuration saved
+
+## Detection Logic
+
+The VCS detector checks (in order of priority):
+
+1. **Platform folders**: `.github/`, `.gitlab/`, `.gitea/`, `.azure/`
+2. **CI config files**: `.gitlab-ci.yml`, `azure-pipelines.yml`, `bitbucket-pipelines.yml`
+3. **Git remote URL**: Parses `.git/config` for github.com, gitlab.com, gitea, codeberg.org, etc.
+4. **Fallback**: `git-only` if `.git/` exists, `none` otherwise
+
+## Impact on Agents
+
+When VCS is configured, agents will:
+
+- **github**: Use `gh pr create`, reference GitHub Actions
+- **gitlab**: Use merge request workflow, reference GitLab CI
+- **azure-devops**: Use `az repos pr create`, reference Azure Pipelines
+- **bitbucket**: Provide manual PR instructions, reference Bitbucket Pipelines
+- **git-only**: Use branch workflow without PR commands
+- **none**: Skip all git-related instructions
+
+## Configuration File
+
+VCS config is stored in `.forge/config.json`:
+
+```json
+{
+  "vcs": {
+    "type": "github",
+    "name": "GitHub",
+    "autoDetected": false,
+    "lastUpdated": "2026-01-16T12:00:00Z"
+  }
+}
+```
+
+## When to Use
+
+- **Initial setup**: Automatically run during `forge init`
+- **Adding git later**: Run `/configure-vcs detect` after `git init`
+- **Switching platforms**: Run `/configure-vcs set <type>` when migrating
+- **Troubleshooting**: Run `/configure-vcs` if agents give wrong git instructions