@hopla/claude-setup 1.2.7 → 1.2.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -89,6 +89,7 @@ After each PIV loop, run `/hopla-execution-report` + `/hopla-system-review` to f
|
|
|
89
89
|
| `/hopla-prime` | Load project context at the start of a session |
|
|
90
90
|
| `/hopla-create-prd` | Create a Product Requirements Document through guided questions |
|
|
91
91
|
| `/hopla-plan-feature` | Research codebase and create a structured implementation plan |
|
|
92
|
+
| `/hopla-review-plan` | Review a plan before execution — get a concise summary and approve |
|
|
92
93
|
| `/hopla-execute` | Execute a structured plan from start to finish with validation |
|
|
93
94
|
| `/hopla-git-commit` | Create a Conventional Commit with Git Flow awareness |
|
|
94
95
|
| `/hopla-git-pr` | Create a GitHub Pull Request with a structured description |
|
|
@@ -112,6 +113,7 @@ After each PIV loop, run `/hopla-execution-report` + `/hopla-system-review` to f
|
|
|
112
113
|
```
|
|
113
114
|
/hopla-prime → load context at session start
|
|
114
115
|
/hopla-plan-feature → research codebase and create plan
|
|
116
|
+
/hopla-review-plan → review plan summary and approve
|
|
115
117
|
/hopla-execute → implement the plan with validation
|
|
116
118
|
/hopla-code-review → technical review of changes
|
|
117
119
|
/hopla-code-review-fix → fix issues found
|
package/files/CLAUDE.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Global Rules — Agentic Coding System
|
|
2
2
|
|
|
3
|
+
> 🌐 **CRITICAL — Language:** Always respond in the same language the user is writing in, regardless of the language of any command or instruction. If the user writes in Spanish, respond in Spanish. If in English, respond in English. This rule overrides everything else.
|
|
4
|
+
|
|
3
5
|
## 1. Communication
|
|
4
6
|
|
|
5
7
|
- **Always respond in the same language the user writes in** — if the user writes in Spanish, respond in Spanish; if in English, respond in English
|
|
@@ -5,8 +5,6 @@ argument-hint: "<plan-file-path>"
|
|
|
5
5
|
|
|
6
6
|
Execute the implementation plan provided. You are the executing agent — you have not seen the planning conversation. The plan is your only source of truth.
|
|
7
7
|
|
|
8
|
-
**Language:** Respond in the same language the user has been writing in throughout this conversation.
|
|
9
|
-
|
|
10
8
|
## Step 1: Load Context
|
|
11
9
|
|
|
12
10
|
Read in this order:
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Review a plan before execution — get a concise summary and approve or request changes
|
|
3
|
+
argument-hint: "<plan-file-path>"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Review the implementation plan and give the executing developer a clear, concise summary before they commit to running it.
|
|
7
|
+
|
|
8
|
+
## Step 1: Read the Plan
|
|
9
|
+
|
|
10
|
+
Read `$1` entirely before doing anything else.
|
|
11
|
+
|
|
12
|
+
## Step 2: Present Executive Summary
|
|
13
|
+
|
|
14
|
+
Do NOT reproduce the full plan. Instead, present a structured summary in the user's language:
|
|
15
|
+
|
|
16
|
+
**Plan: [Feature Name]**
|
|
17
|
+
|
|
18
|
+
**What is being built:**
|
|
19
|
+
[2-3 sentences max — what the feature does and why]
|
|
20
|
+
|
|
21
|
+
**Tasks ([N] total):**
|
|
22
|
+
| # | Action | File | Risk |
|
|
23
|
+
|---|--------|------|------|
|
|
24
|
+
| 1 | create/modify/delete | `path/to/file` | ⚠️ gotcha if any / — |
|
|
25
|
+
| 2 | ... | ... | ... |
|
|
26
|
+
|
|
27
|
+
**Files touched:** [count] files — [list key ones]
|
|
28
|
+
|
|
29
|
+
**Validation plan:**
|
|
30
|
+
- [ ] [exact lint command]
|
|
31
|
+
- [ ] [exact type check command]
|
|
32
|
+
- [ ] [exact test command]
|
|
33
|
+
- [ ] [integration check]
|
|
34
|
+
|
|
35
|
+
**Acceptance criteria:**
|
|
36
|
+
- [ ] [criterion 1]
|
|
37
|
+
- [ ] [criterion 2]
|
|
38
|
+
|
|
39
|
+
**⚠️ Watch out for:**
|
|
40
|
+
[List any gotchas, risks, or dependencies flagged in the plan. If none, say "Nothing flagged."]
|
|
41
|
+
|
|
42
|
+
## Step 3: Ask for Approval
|
|
43
|
+
|
|
44
|
+
After the summary, ask:
|
|
45
|
+
> "¿Todo claro? Puedes aprobar para ejecutar, pedir cambios, o hacer preguntas sobre alguna tarea."
|
|
46
|
+
> (or in English if the conversation is in English)
|
|
47
|
+
|
|
48
|
+
**Review loop:**
|
|
49
|
+
- If the user has questions → answer them based on the plan content
|
|
50
|
+
- If the user requests changes → note them and tell the user to ask Robert to update the plan, or apply minor clarifications directly if they are unambiguous
|
|
51
|
+
- If the user approves → confirm: "✅ Plan approved. Run `/hopla-execute $1` to start."
|