@hopla/claude-setup 1.10.2 → 1.11.1

package/skills/hopla-verify/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: hopla-verify
+description: "Verification gate that ensures all completion claims are backed by fresh evidence. Use when the agent is about to declare work as done, finished, complete, ready, or implemented. Also use when hearing 'listo', 'terminé', 'ya está', 'done', 'finished', 'all tests pass', 'everything works', or any completion claim. Do NOT use for intermediate progress updates or partial task completion."
+---
+
+# Verification Before Completion
+
+## Iron Law
+**NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.**
+
+Never declare work as done based on memory, assumptions, or previous outputs. Every claim must be backed by a fresh execution right now.
+
+## Gate Process
+
+When about to declare any task as complete:
+
+1. **IDENTIFY** — What verification command(s) confirm this claim?
+2. **EXECUTE** — Run the verification fresh (never reuse previous output)
+3. **READ** — Read the complete output carefully
+4. **VERIFY** — Confirm the output actually proves the claim
+5. **ONLY THEN** — Declare the work complete with evidence
+
+## What Requires What Evidence
+
+| Claim | Required Evidence |
+|-------|------------------|
+| "Tests pass" | Fresh `npm test` / `pytest` / test runner output showing all green |
+| "Build succeeds" | Fresh build command output with no errors |
+| "Lint is clean" | Fresh linter output showing 0 errors |
+| "Types check" | Fresh `tsc --noEmit` / type checker output |
+| "Feature works" | Demonstrate the feature running (test or manual verification) |
+| "Bug is fixed" | Test that reproduces the bug now passes |
+| "No regressions" | Full test suite passes, not just new tests |
+
+## Prohibited Phrases Before Verification
+
+These phrases are RED FLAGS — never use them without fresh evidence:
+
+- "should work" / "debería funcionar"
+- "probably passes" / "probablemente pase"
+- "seems to be fine" / "parece estar bien"
+- "I believe this fixes" / "creo que esto arregla"
+- "this should resolve" / "esto debería resolver"
+- "looks correct" / "se ve correcto"
+
+Instead, run the verification and report actual results.
+
+## Integration with Validation Pyramid
+
+When completing a feature (not just a single file edit), run the full validation pyramid:
+
+1. **Level 1**: Lint & format
+2. **Level 2**: Type check
+3. **Level 3**: Unit tests
+4. **Level 4**: Integration tests (if applicable)
+5. **Level 5**: Human review suggestion
+
+Reference `/hopla-validate` for project-specific validation commands.
+
+## Scope
+
+- **Applies to**: Any declaration of completion, whether mid-conversation or at end of task
+- **Does NOT apply to**: Intermediate progress updates ("I've finished editing file X, moving to file Y")
+- **Partial completion**: You may say "file X is updated" without full validation, but "the feature is complete" requires the full gate

package/skills/hopla-worktree/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: hopla-worktree
+description: "Git worktree management for isolated feature development. Use when starting a new feature that benefits from isolation, when the user says 'worktree', 'isolated branch', 'parallel development', or when implementing multiple features simultaneously. Do NOT use for quick fixes or single-file changes."
+---
+
+# Git Worktrees for Isolated Development
+
+## What Are Worktrees?
+Git worktrees create separate working directories for different branches, sharing the same git history. Each worktree is an independent workspace.
+
+## When to Use
+- Starting a feature that should be isolated from other work
+- Developing multiple features in parallel
+- Needing a clean baseline to test against
+- Working on a risky change that might need to be abandoned
+
+## Setup Process
+
+### Step 1: Choose Worktree Directory
+Check in order:
+1. Existing `.worktrees/` or `worktrees/` directory
+2. CLAUDE.md preference (if configured)
+3. Ask the user
+
+### Step 2: Ensure Directory is Gitignored
+```bash
+# Verify the worktree directory is in .gitignore
+grep -q "worktrees" .gitignore || echo "worktrees/" >> .gitignore
+```
+
+### Step 3: Create Worktree
+```bash
+# Create worktree with a new feature branch
+git worktree add worktrees/feature-name -b feature/feature-name
+```
+
+### Step 4: Setup Project in Worktree
+Auto-detect and run setup:
+- **Node.js**: `npm install` or `yarn install`
+- **Python**: `pip install -r requirements.txt` or `poetry install`
+- **Rust**: `cargo build`
+- **Go**: `go mod download`
+
+### Step 5: Verify Clean Baseline
+```bash
+cd worktrees/feature-name
+# Run tests to ensure baseline is green
+npm test  # or equivalent
+```
+
+If tests fail before any changes, STOP and report — the baseline is broken.
+
+### Step 6: Work in the Worktree
+All work for this feature happens in `worktrees/feature-name/`.
+
+## Cleanup
+
+### After Merge
+```bash
+git worktree remove worktrees/feature-name
+git branch -d feature/feature-name
+```
+
+### If Abandoned
+```bash
+git worktree remove --force worktrees/feature-name
+git branch -D feature/feature-name
+```
+
+## Integration
+- Use with `/hopla-execute` for isolated feature implementation
+- Use with `/hopla-git-pr` for creating PRs from the worktree branch
+- Combine with parallel dispatch for multiple features simultaneously