@hopla/claude-setup 1.2.4 → 1.2.6

package/README.md

@@ -90,7 +90,8 @@ After each PIV loop, run `/hopla-execution-report` + `/hopla-system-review` to f
 | `/hopla-create-prd` | Create a Product Requirements Document through guided questions |
 | `/hopla-plan-feature` | Research codebase and create a structured implementation plan |
 | `/hopla-execute` | Execute a structured plan from start to finish with validation |
-| `/hopla-commit` | Create a Conventional Commit with Git Flow awareness |
+| `/hopla-git-commit` | Create a Conventional Commit with Git Flow awareness |
+| `/hopla-git-pr` | Create a GitHub Pull Request with a structured description |
 | `/hopla-code-review` | Technical code review on recently changed files |
 | `/hopla-code-review-fix` | Fix issues found in a code review report |
 | `/hopla-execution-report` | Generate an implementation report for system review |
@@ -104,7 +105,7 @@ After each PIV loop, run `/hopla-execution-report` + `/hopla-system-review` to f
 ```
 /hopla-init-project   → creates CLAUDE.md + .agents/ structure
 /hopla-create-prd     → defines product scope (PRD.md)
-/hopla-commit         → saves Layer 1 foundation to git
+/hopla-git-commit     → saves Layer 1 foundation to git
 ```
 
 ### Feature development (PIV loop)
@@ -114,7 +115,8 @@ After each PIV loop, run `/hopla-execution-report` + `/hopla-system-review` to f
 /hopla-execute        → implement the plan with validation
 /hopla-code-review    → technical review of changes
 /hopla-code-review-fix → fix issues found
-/hopla-commit         → save to git
+/hopla-git-commit     → save to git
+/hopla-git-pr         → open pull request on GitHub
 ```
 
 ### After implementation
@@ -156,7 +158,7 @@ Commands are modular — the output of one becomes the input of the next. Some c
 /hopla-code-review-fix .agents/code-reviews/add-user-authentication.md
 
 # 5. Commit
-/hopla-commit
+/hopla-git-commit
 
 # 6. Document
 /hopla-execution-report

package/cli.js

@@ -108,6 +108,7 @@ const LEGACY_FILES = [
     "prime.md",
     "system-review.md",
     "hopla-lang.md",
+    "hopla-commit.md",
 ];
 
 function removeLegacyFiles() {

package/files/commands/hopla-create-prd.md

@@ -201,17 +201,17 @@ Do NOT show the full PRD in the chat. Instead:
 1. Save the draft to `PRD.draft.md` at the project root
 2. Save any on-demand context documents created in Step 3 (also with `.draft` suffix if new)
 3. Tell the user:
-   > "Draft saved to `PRD.draft.md` — open it in your editor. You can add `<? your note ?>` comments anywhere in the file and tell me 'apply comments', request changes in chat, or say 'looks good' to finalize."
+   > "Draft saved to `PRD.draft.md` — open it in your editor and review it carefully. If you want changes, add comments like `<? change this >` anywhere in the file and tell me 'apply comments'. You can also request changes directly in the chat. When it's ready, say 'done' to create the final file."
 
 **Review loop:** Stay in this loop until the user finalizes:
 
-- If the user says **"apply comments"** (or similar) → scan `PRD.draft.md` for `<? ... ?>` comments, apply each one, remove the comment tags, update the file, then list what was changed: "Applied 3 changes: [list]. Anything else, or ready to finalize?"
+- If the user says **"apply comments"** (or similar) → scan `PRD.draft.md` for `<? ... >` comments, apply each one, remove the comment tags, update the file, then list what was changed: "Applied 3 changes: [list]. Anything else, or ready to finalize?"
 - If the user requests changes in chat → apply them directly to `PRD.draft.md`, then say: "Updated — anything else, or ready to finalize?"
 - If the user says the draft is ready (e.g. "looks good", "finalize", "listo") → proceed to Step 6
 
 **Comment format the user can add directly in the draft:**
 ```
-<? your instruction here ?>
+<? your instruction here >
 ```
 Comments can be placed anywhere in the file — inline after a line, or on their own line above a section. Process them in order from top to bottom.
 
@@ -222,4 +222,4 @@ Do not ask clarifying questions about changes — just apply them and confirm wh
 1. Rename `PRD.draft.md` → `PRD.md` (overwrite if it existed)
 2. Rename any `.draft` context documents to their final names
 3. Delete all `.draft` files
-4. Confirm: "✅ `PRD.md` saved. Run `/hopla-commit` to save it to the repository."
+4. Confirm: "✅ `PRD.md` saved. Run `/hopla-git-commit` to save it to the repository."

package/files/commands/hopla-execute.md

@@ -110,4 +110,4 @@ Provide a summary of what was done:
 After the summary, suggest:
 1. Run `/hopla-execution-report` to document this implementation for system review
 2. Run `/hopla-code-review` for a technical quality check
-3. Run `/hopla-commit` once everything is approved
+3. Run `/hopla-git-commit` once everything is approved

package/files/commands/hopla-git-pr.md

@@ -0,0 +1,82 @@
+---
+description: Create a GitHub Pull Request with a structured description
+argument-hint: "[optional: base branch, defaults to develop]"
+---
+
+Create a Pull Request on GitHub for the current branch.
+
+## Step 1: Gather Context
+
+```bash
+git status
+git branch --show-current
+git log --oneline origin/$(git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null | sed 's|.*/||' || echo 'develop')..HEAD
+git diff --stat origin/$(git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null | sed 's|.*/||' || echo 'develop')..HEAD
+```
+
+Read the following if they exist:
+- The plan file in `.agents/plans/` related to this feature
+- `CLAUDE.md` — for project context
+
+## Step 2: Determine Base Branch
+
+- If `$1` is provided, use it as the base branch
+- Otherwise default to `develop` (or `dev` if that's what the project uses)
+- If on `main` or `develop` directly, warn the user: "You're on `[branch]` — PRs should come from feature branches."
+
+## Step 3: Check Push Status
+
+```bash
+git status
+```
+
+If the branch hasn't been pushed yet:
+> "Branch not pushed yet. Push to origin first?"
+
+Wait for confirmation before pushing:
+```bash
+git push -u origin <branch>
+```
+
+## Step 4: Build PR Description
+
+Using the commits and plan context, draft:
+
+**Title:** `[type(scope)]: short description` — match the main commit or feature name, max 70 chars
+
+**Body:**
+```markdown
+## Summary
+- [What was built — 2-3 bullets max]
+
+## Changes
+- [Key files modified and why]
+
+## Test Plan
+- [ ] [How to verify this works]
+- [ ] [Edge cases to check]
+
+## Related
+- Plan: `.agents/plans/[feature-name].md` (if exists)
+```
+
+## Step 5: Propose and Confirm
+
+Show the proposed PR title and body to the user:
+> "Proposed PR:
+> Title: `[title]`
+> Base: `[base branch]`
+> [body preview]
+> Shall I create it?"
+
+Wait for explicit approval before creating.
+
+## Step 6: Create PR
+
+```bash
+gh pr create --title "[title]" --body "[body]" --base [base-branch]
+```
+
+After creating, show the PR URL to the user.
+
+**Never merge automatically** — the PR is for human review.

package/files/commands/hopla-init-project.md

@@ -258,4 +258,4 @@ Once confirmed:
 2. Create `.agents/` directory structure
 3. Update `.gitignore`
 4. Tell the user: "Project initialized. Run `/hopla-create-prd` next to define the product scope, or `/hopla-plan-feature` to start planning a feature."
-5. Suggest running `/hopla-commit` to save everything
+5. Suggest running `/hopla-git-commit` to save everything

package/files/commands/hopla-plan-feature.md

@@ -134,16 +134,16 @@ Before saving the draft, review the plan against these criteria:
 
 1. Save the plan to `.agents/plans/[kebab-case-feature-name].draft.md`
 2. Tell the user:
-   > "Plan draft saved to `.agents/plans/[feature-name].draft.md` — open it in your editor. You can add `<? your note ?>` comments anywhere and tell me 'apply comments', request changes in chat, or say 'looks good' to finalize."
+   > "Plan draft saved to `.agents/plans/[feature-name].draft.md` — open it in your editor and review it carefully. If you want changes, add comments like `<? change this >` anywhere in the file and tell me 'apply comments'. You can also request changes directly in the chat. When it's ready, say 'done' to create the final file."
 3. Also mention:
    - How many tasks are in the plan
    - Any open questions or decisions that require human input before execution
 
 **Review loop:** Stay in this loop until the user finalizes:
-- If the user says **"apply comments"** → scan the draft for `<? ... ?>`, apply each one, remove the comment tags, update the file, report what changed
+- If the user says **"apply comments"** → scan the draft for `<? ... >`, apply each one, remove the comment tags, update the file, report what changed
 - If the user requests changes in chat → apply directly to the draft, confirm what changed
 - If the user says the plan is ready → proceed to finalize
 
 **Finalize:**
 1. Rename `.agents/plans/[feature-name].draft.md` → `.agents/plans/[feature-name].md`
-2. Confirm: "✅ Plan saved to `.agents/plans/[feature-name].md`. Run `/hopla-execute .agents/plans/[feature-name].md` to implement it, or `/hopla-commit` to save the plan first."
+2. Confirm: "✅ Plan saved to `.agents/plans/[feature-name].md`. Run `/hopla-execute .agents/plans/[feature-name].md` to implement it, or `/hopla-git-commit` to save the plan first."

package/files/commands/hopla-prime.md

@@ -29,14 +29,31 @@ git log --oneline -10
 git status
 ```
 
-## Step 4: Summary Report
+## Step 4: Check Pending Work
 
-Write a short, conversational message (2-4 sentences) addressed directly to the user. Mention:
+```bash
+ls .agents/plans/ 2>/dev/null
+```
+
+If `.agents/plans/` exists, identify:
+- `.draft.md` files — unfinished drafts waiting for review
+- `.md` files (without `.draft`) — finalized plans ready to execute
+
+## Step 5: Summary Report
+
+Write a short, conversational message addressed directly to the user. Mention:
 - What the project is and what it does
 - The current branch and what it's for
 - Whether there are uncommitted changes or pending work
 - The command to start the project (if available)
 
+If there are pending plans, list them clearly after the prose summary:
+```
+Pending plans:
+- inventory-page.draft.md ← draft, not finalized yet
+- add-user-authentication.md ← ready to execute with /hopla-execute
+```
+
 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.
 
-Do NOT use headers, labels, or bullet points in this final message. Write it as natural, friendly prose.
+Do NOT use headers in the prose summary. Write it as natural, friendly prose, then the pending plans list if applicable.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hopla/claude-setup",
-  "version": "1.2.4",
+  "version": "1.2.6",
   "description": "Hopla team agentic coding system for Claude Code",
   "type": "module",
   "bin": {