@hopla/claude-setup 1.0.2 → 1.0.4
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 +16 -10
- package/files/commands/{prime.md → hopla-prime.md} +7 -8
- package/package.json +1 -1
- /package/files/commands/{code-review-fix.md → hopla-code-review-fix.md} +0 -0
- /package/files/commands/{code-review.md → hopla-code-review.md} +0 -0
- /package/files/commands/{commit.md → hopla-commit.md} +0 -0
- /package/files/commands/{create-prd.md → hopla-create-prd.md} +0 -0
- /package/files/commands/{execute.md → hopla-execute.md} +0 -0
- /package/files/commands/{execution-report.md → hopla-execution-report.md} +0 -0
- /package/files/commands/{plan-feature.md → hopla-plan-feature.md} +0 -0
- /package/files/commands/{system-review.md → hopla-system-review.md} +0 -0
package/README.md
CHANGED
|
@@ -5,13 +5,27 @@ Hopla team agentic coding system for Claude Code. Installs global rules and comm
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
|
-
|
|
8
|
+
npm install -g @hopla/claude-setup
|
|
9
|
+
claude-setup
|
|
9
10
|
```
|
|
10
11
|
|
|
11
12
|
To overwrite existing files without prompting:
|
|
12
13
|
|
|
13
14
|
```bash
|
|
14
|
-
|
|
15
|
+
claude-setup --force
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
## Update
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
npm install -g @hopla/claude-setup@latest
|
|
22
|
+
claude-setup --force
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
## Uninstall
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
claude-setup --uninstall
|
|
15
29
|
```
|
|
16
30
|
|
|
17
31
|
## What gets installed
|
|
@@ -31,11 +45,3 @@ npx @hopla/claude-setup --force
|
|
|
31
45
|
| `/code-review-fix` | Fix issues found in a code review report |
|
|
32
46
|
| `/execution-report` | Generate an implementation report for system review |
|
|
33
47
|
| `/system-review` | Analyze implementation against plan to find process improvements |
|
|
34
|
-
|
|
35
|
-
## Update
|
|
36
|
-
|
|
37
|
-
Re-run the install command to update to the latest version:
|
|
38
|
-
|
|
39
|
-
```bash
|
|
40
|
-
npx @hopla/claude-setup@latest
|
|
41
|
-
```
|
|
@@ -31,13 +31,12 @@ git status
|
|
|
31
31
|
|
|
32
32
|
## Step 4: Summary Report
|
|
33
33
|
|
|
34
|
-
|
|
34
|
+
Write a short, conversational message (2-4 sentences) addressed directly to the user. Mention:
|
|
35
|
+
- What the project is and what it does
|
|
36
|
+
- The current branch and what it's for
|
|
37
|
+
- Whether there are uncommitted changes or pending work
|
|
38
|
+
- The command to start the project (if available)
|
|
35
39
|
|
|
36
|
-
|
|
37
|
-
**Stack:** [languages, frameworks, key libraries]
|
|
38
|
-
**Current branch:** [branch name and what it's for]
|
|
39
|
-
**Key structure:** [main folders and their purpose]
|
|
40
|
-
**Useful commands:** [how to run, test, build]
|
|
41
|
-
**Git status:** [clean / changes pending / uncommitted files]
|
|
40
|
+
End with a sentence like: "Listo para continuar — ¿por dónde empezamos?" or "All caught up — what are we working on today?" depending on the language the user writes in.
|
|
42
41
|
|
|
43
|
-
|
|
42
|
+
Do NOT use headers, labels, or bullet points in this final message. Write it as natural, friendly prose.
|
package/package.json
CHANGED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|