@funnycode/myclaude 0.1.71 → 0.1.73

package/seed/marketplaces/ecc/commands/pr.md

@@ -1,184 +1,184 @@
----
-description: "Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes"
-argument-hint: "[base-branch] (default: main)"
----
-
-# Create Pull Request
-
-**Input**: `$ARGUMENTS` — optional, may contain a base branch name and/or flags (e.g., `--draft`).
-
-**Parse `$ARGUMENTS`**:
-- Extract any recognized flags (`--draft`)
-- Treat remaining non-flag text as the base branch name
-- Default base branch to `main` if none specified
-
----
-
-## Phase 1 — VALIDATE
-
-Check preconditions:
-
-```bash
-git branch --show-current
-git status --short
-git log origin/<base>..HEAD --oneline
-```
-
-| Check | Condition | Action if Failed |
-|---|---|---|
-| Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." |
-| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first." |
-| Has commits ahead | `git log origin/<base>..HEAD` not empty | Stop: "No commits ahead of `<base>`. Nothing to PR." |
-| No existing PR | `gh pr list --head <branch> --json number` is empty | Stop: "PR already exists: #<number>. Use `gh pr view <number> --web` to open it." |
-
-If all checks pass, proceed.
-
----
-
-## Phase 2 — DISCOVER
-
-### PR Template
-
-Search for PR template in order:
-
-1. `.github/PULL_REQUEST_TEMPLATE/` directory — if exists, list files and let user choose (or use `default.md`)
-2. `.github/PULL_REQUEST_TEMPLATE.md`
-3. `.github/pull_request_template.md`
-4. `docs/pull_request_template.md`
-
-If found, read it and use its structure for the PR body.
-
-### Commit Analysis
-
-```bash
-git log origin/<base>..HEAD --format="%h %s" --reverse
-```
-
-Analyze commits to determine:
-- **PR title**: Use conventional commit format with type prefix — `feat: ...`, `fix: ...`, etc.
-  - If multiple types, use the dominant one
-  - If single commit, use its message as-is
-- **Change summary**: Group commits by type/area
-
-### File Analysis
-
-```bash
-git diff origin/<base>..HEAD --stat
-git diff origin/<base>..HEAD --name-only
-```
-
-Categorize changed files: source, tests, docs, config, migrations.
-
-### Planning Artifacts
-
-Check for related artifacts produced by `/plan-prd`, `/plan`, or the legacy PRP workflow:
-- `.claude/prds/` — PRDs this PR implements a milestone of
-- `.claude/plans/` — Plans executed by this PR
-- `.claude/PRPs/prds/` — legacy PRP PRDs
-- `.claude/PRPs/plans/` — legacy PRP implementation plans
-- `.claude/PRPs/reports/` — legacy PRP implementation reports
-
-Reference these in the PR body if they exist.
-
----
-
-## Phase 3 — PUSH
-
-```bash
-git push -u origin HEAD
-```
-
-If push fails due to divergence:
-```bash
-git fetch origin
-git rebase origin/<base>
-git push -u origin HEAD
-```
-
-If rebase conflicts occur, stop and inform the user.
-
----
-
-## Phase 4 — CREATE
-
-### With Template
-
-If a PR template was found in Phase 2, fill in each section using the commit and file analysis. Preserve all template sections — leave sections as "N/A" if not applicable rather than removing them.
-
-### Without Template
-
-Use this default format:
-
-```markdown
-## Summary
-
-<1-2 sentence description of what this PR does and why>
-
-## Changes
-
-<bulleted list of changes grouped by area>
-
-## Files Changed
-
-<table or list of changed files with change type: Added/Modified/Deleted>
-
-## Testing
-
-<description of how changes were tested, or "Needs testing">
-
-## Related Issues
-
-<linked issues with Closes/Fixes/Relates to #N, or "None">
-```
-
-### Create the PR
-
-```bash
-gh pr create \
-  --title "<PR title>" \
-  --base <base-branch> \
-  --body "<PR body>"
-  # Add --draft if the --draft flag was parsed from $ARGUMENTS
-```
-
----
-
-## Phase 5 — VERIFY
-
-```bash
-gh pr view --json number,url,title,state,baseRefName,headRefName,additions,deletions,changedFiles
-gh pr checks --json name,status,conclusion 2>/dev/null || true
-```
-
----
-
-## Phase 6 — OUTPUT
-
-Report to user:
-
-```
-PR #<number>: <title>
-URL: <url>
-Branch: <head> → <base>
-Changes: +<additions> -<deletions> across <changedFiles> files
-
-CI Checks: <status summary or "pending" or "none configured">
-
-Artifacts referenced:
-  - <any PRDs/plans linked in PR body>
-
-Next steps:
-  - gh pr view <number> --web   → open in browser
-  - /code-review <number>       → review the PR
-  - gh pr merge <number>        → merge when ready
-```
-
----
-
-## Edge Cases
-
-- **No `gh` CLI**: Stop with: "GitHub CLI (`gh`) is required. Install: <https://cli.github.com/>"
-- **Not authenticated**: Stop with: "Run `gh auth login` first."
-- **Force push needed**: If remote has diverged and rebase was done, use `git push --force-with-lease` (never `--force`).
-- **Multiple PR templates**: If `.github/PULL_REQUEST_TEMPLATE/` has multiple files, list them and ask user to choose.
-- **Large PR (>20 files)**: Warn about PR size. Suggest splitting if changes are logically separable.
+---
+description: "Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes"
+argument-hint: "[base-branch] (default: main)"
+---
+
+# Create Pull Request
+
+**Input**: `$ARGUMENTS` — optional, may contain a base branch name and/or flags (e.g., `--draft`).
+
+**Parse `$ARGUMENTS`**:
+- Extract any recognized flags (`--draft`)
+- Treat remaining non-flag text as the base branch name
+- Default base branch to `main` if none specified
+
+---
+
+## Phase 1 — VALIDATE
+
+Check preconditions:
+
+```bash
+git branch --show-current
+git status --short
+git log origin/<base>..HEAD --oneline
+```
+
+| Check | Condition | Action if Failed |
+|---|---|---|
+| Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." |
+| Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first." |
+| Has commits ahead | `git log origin/<base>..HEAD` not empty | Stop: "No commits ahead of `<base>`. Nothing to PR." |
+| No existing PR | `gh pr list --head <branch> --json number` is empty | Stop: "PR already exists: #<number>. Use `gh pr view <number> --web` to open it." |
+
+If all checks pass, proceed.
+
+---
+
+## Phase 2 — DISCOVER
+
+### PR Template
+
+Search for PR template in order:
+
+1. `.github/PULL_REQUEST_TEMPLATE/` directory — if exists, list files and let user choose (or use `default.md`)
+2. `.github/PULL_REQUEST_TEMPLATE.md`
+3. `.github/pull_request_template.md`
+4. `docs/pull_request_template.md`
+
+If found, read it and use its structure for the PR body.
+
+### Commit Analysis
+
+```bash
+git log origin/<base>..HEAD --format="%h %s" --reverse
+```
+
+Analyze commits to determine:
+- **PR title**: Use conventional commit format with type prefix — `feat: ...`, `fix: ...`, etc.
+  - If multiple types, use the dominant one
+  - If single commit, use its message as-is
+- **Change summary**: Group commits by type/area
+
+### File Analysis
+
+```bash
+git diff origin/<base>..HEAD --stat
+git diff origin/<base>..HEAD --name-only
+```
+
+Categorize changed files: source, tests, docs, config, migrations.
+
+### Planning Artifacts
+
+Check for related artifacts produced by `/plan-prd`, `/plan`, or the legacy PRP workflow:
+- `.claude/prds/` — PRDs this PR implements a milestone of
+- `.claude/plans/` — Plans executed by this PR
+- `.claude/PRPs/prds/` — legacy PRP PRDs
+- `.claude/PRPs/plans/` — legacy PRP implementation plans
+- `.claude/PRPs/reports/` — legacy PRP implementation reports
+
+Reference these in the PR body if they exist.
+
+---
+
+## Phase 3 — PUSH
+
+```bash
+git push -u origin HEAD
+```
+
+If push fails due to divergence:
+```bash
+git fetch origin
+git rebase origin/<base>
+git push -u origin HEAD
+```
+
+If rebase conflicts occur, stop and inform the user.
+
+---
+
+## Phase 4 — CREATE
+
+### With Template
+
+If a PR template was found in Phase 2, fill in each section using the commit and file analysis. Preserve all template sections — leave sections as "N/A" if not applicable rather than removing them.
+
+### Without Template
+
+Use this default format:
+
+```markdown
+## Summary
+
+<1-2 sentence description of what this PR does and why>
+
+## Changes
+
+<bulleted list of changes grouped by area>
+
+## Files Changed
+
+<table or list of changed files with change type: Added/Modified/Deleted>
+
+## Testing
+
+<description of how changes were tested, or "Needs testing">
+
+## Related Issues
+
+<linked issues with Closes/Fixes/Relates to #N, or "None">
+```
+
+### Create the PR
+
+```bash
+gh pr create \
+  --title "<PR title>" \
+  --base <base-branch> \
+  --body "<PR body>"
+  # Add --draft if the --draft flag was parsed from $ARGUMENTS
+```
+
+---
+
+## Phase 5 — VERIFY
+
+```bash
+gh pr view --json number,url,title,state,baseRefName,headRefName,additions,deletions,changedFiles
+gh pr checks --json name,status,conclusion 2>/dev/null || true
+```
+
+---
+
+## Phase 6 — OUTPUT
+
+Report to user:
+
+```
+PR #<number>: <title>
+URL: <url>
+Branch: <head> → <base>
+Changes: +<additions> -<deletions> across <changedFiles> files
+
+CI Checks: <status summary or "pending" or "none configured">
+
+Artifacts referenced:
+  - <any PRDs/plans linked in PR body>
+
+Next steps:
+  - gh pr view <number> --web   → open in browser
+  - /code-review <number>       → review the PR
+  - gh pr merge <number>        → merge when ready
+```
+
+---
+
+## Edge Cases
+
+- **No `gh` CLI**: Stop with: "GitHub CLI (`gh`) is required. Install: <https://cli.github.com/>"
+- **Not authenticated**: Stop with: "Run `gh auth login` first."
+- **Force push needed**: If remote has diverged and rebase was done, use `git push --force-with-lease` (never `--force`).
+- **Multiple PR templates**: If `.github/PULL_REQUEST_TEMPLATE/` has multiple files, list them and ask user to choose.
+- **Large PR (>20 files)**: Warn about PR size. Suggest splitting if changes are logically separable.

package/seed/marketplaces/ecc/commands/project-init.md

@@ -1,86 +1,86 @@
----
-description: Detect a project's stack and produce a dry-run ECC onboarding plan using the repository's install manifests and stack mappings.
----
-
-# /project-init
-
-Create a safe, reviewable ECC onboarding plan for the current project. This command should start in dry-run mode and only write files after explicit user approval.
-
-## Usage
-
-```text
-/project-init
-/project-init --dry-run
-/project-init --target claude
-/project-init --target cursor
-/project-init --skills continuous-learning-v2,security-review
-/project-init --config ecc-install.json
-```
-
-## Safety Rules
-
-1. Default to dry-run. Do not modify `CLAUDE.md`, settings files, rules, skills, or install state until the user approves the concrete plan.
-2. Preserve existing project guidance. If `CLAUDE.md`, `.claude/settings.local.json`, `.cursor/`, `.codex/`, `.gemini/`, `.opencode/`, `.codebuddy/`, `.joycode/`, or `.qwen/` already exists, inspect it and propose a merge/append plan instead of overwriting.
-3. Use ECC's installer and manifest tooling. Do not hand-copy files or clone arbitrary remotes as an install shortcut.
-4. Keep permissions narrow. Any generated settings should match detected build/test/lint tools and avoid broad shell access.
-5. Report exactly what would change before applying anything.
-
-## Detection Inputs
-
-Read the current project root and detect stack signals from:
-
-- package manager files: `package.json`, `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lockb`
-- language manifests: `pyproject.toml`, `requirements.txt`, `go.mod`, `Cargo.toml`, `pom.xml`, `build.gradle`, `build.gradle.kts`
-- framework files: `next.config.*`, `vite.config.*`, `tailwind.config.*`, `Dockerfile`, `docker-compose.yml`
-- ECC config: `ecc-install.json`
-- optional stack map: `config/project-stack-mappings.json` in the ECC repo
-
-When the ECC checkout is available, use `config/project-stack-mappings.json` as the stack-to-rules/skills reference. If the file is unavailable, fall back to the installed ECC manifests and explicit user choices.
-
-## Planning Flow
-
-1. Identify the target harness. Default to `claude` unless the user asks for `cursor`, `codex`, `gemini`, `opencode`, `codebuddy`, `joycode`, or `qwen`.
-2. Detect stacks from project files and show the evidence for each match.
-3. Resolve the smallest useful ECC plan:
-   - project has an `ecc-install.json`: `node scripts/install-plan.js --config ecc-install.json --json`
-   - user named a profile: `node scripts/install-plan.js --profile <profile> --target <target> --json`
-   - user named skills: `node scripts/install-plan.js --skills <skill-ids> --target <target> --json`
-   - only language stacks are detected: use the legacy language install dry-run with those language names
-4. Run a dry-run apply command before writing:
-
-```bash
-node scripts/install-apply.js --target <target> --dry-run --json <language-or-profile-args>
-```
-
-5. Summarize detected stacks, selected modules/components/skills, target paths, skipped unsupported modules, and files that would be changed.
-6. Ask for approval before applying the non-dry-run command.
-
-## Output Contract
-
-Return:
-
-1. detected stack evidence
-2. proposed target harness
-3. exact dry-run command used
-4. exact apply command to run after approval
-5. files/directories that would be created or changed
-6. warnings about existing files, broad permissions, missing scripts, or unsupported targets
-
-## CLAUDE.md Guidance
-
-If the user wants a `CLAUDE.md` starter, generate it separately from the installer plan and keep it minimal:
-
-- build command, if detected
-- test command, if detected
-- lint/typecheck command, if detected
-- dev server command, if detected
-- repo-specific notes from existing package scripts or manifests
-
-Never replace an existing `CLAUDE.md` without showing a diff and receiving approval.
-
-## Related
-
-- `config/project-stack-mappings.json` for stack-to-surface hints
-- `scripts/install-plan.js` for deterministic plan resolution
-- `scripts/install-apply.js` for dry-run and apply operations
-- `/ecc-guide` for interactive feature discovery before installing
+---
+description: Detect a project's stack and produce a dry-run ECC onboarding plan using the repository's install manifests and stack mappings.
+---
+
+# /project-init
+
+Create a safe, reviewable ECC onboarding plan for the current project. This command should start in dry-run mode and only write files after explicit user approval.
+
+## Usage
+
+```text
+/project-init
+/project-init --dry-run
+/project-init --target claude
+/project-init --target cursor
+/project-init --skills continuous-learning-v2,security-review
+/project-init --config ecc-install.json
+```
+
+## Safety Rules
+
+1. Default to dry-run. Do not modify `CLAUDE.md`, settings files, rules, skills, or install state until the user approves the concrete plan.
+2. Preserve existing project guidance. If `CLAUDE.md`, `.claude/settings.local.json`, `.cursor/`, `.codex/`, `.gemini/`, `.opencode/`, `.codebuddy/`, `.joycode/`, or `.qwen/` already exists, inspect it and propose a merge/append plan instead of overwriting.
+3. Use ECC's installer and manifest tooling. Do not hand-copy files or clone arbitrary remotes as an install shortcut.
+4. Keep permissions narrow. Any generated settings should match detected build/test/lint tools and avoid broad shell access.
+5. Report exactly what would change before applying anything.
+
+## Detection Inputs
+
+Read the current project root and detect stack signals from:
+
+- package manager files: `package.json`, `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lockb`
+- language manifests: `pyproject.toml`, `requirements.txt`, `go.mod`, `Cargo.toml`, `pom.xml`, `build.gradle`, `build.gradle.kts`
+- framework files: `next.config.*`, `vite.config.*`, `tailwind.config.*`, `Dockerfile`, `docker-compose.yml`
+- ECC config: `ecc-install.json`
+- optional stack map: `config/project-stack-mappings.json` in the ECC repo
+
+When the ECC checkout is available, use `config/project-stack-mappings.json` as the stack-to-rules/skills reference. If the file is unavailable, fall back to the installed ECC manifests and explicit user choices.
+
+## Planning Flow
+
+1. Identify the target harness. Default to `claude` unless the user asks for `cursor`, `codex`, `gemini`, `opencode`, `codebuddy`, `joycode`, or `qwen`.
+2. Detect stacks from project files and show the evidence for each match.
+3. Resolve the smallest useful ECC plan:
+   - project has an `ecc-install.json`: `node scripts/install-plan.js --config ecc-install.json --json`
+   - user named a profile: `node scripts/install-plan.js --profile <profile> --target <target> --json`
+   - user named skills: `node scripts/install-plan.js --skills <skill-ids> --target <target> --json`
+   - only language stacks are detected: use the legacy language install dry-run with those language names
+4. Run a dry-run apply command before writing:
+
+```bash
+node scripts/install-apply.js --target <target> --dry-run --json <language-or-profile-args>
+```
+
+5. Summarize detected stacks, selected modules/components/skills, target paths, skipped unsupported modules, and files that would be changed.
+6. Ask for approval before applying the non-dry-run command.
+
+## Output Contract
+
+Return:
+
+1. detected stack evidence
+2. proposed target harness
+3. exact dry-run command used
+4. exact apply command to run after approval
+5. files/directories that would be created or changed
+6. warnings about existing files, broad permissions, missing scripts, or unsupported targets
+
+## CLAUDE.md Guidance
+
+If the user wants a `CLAUDE.md` starter, generate it separately from the installer plan and keep it minimal:
+
+- build command, if detected
+- test command, if detected
+- lint/typecheck command, if detected
+- dev server command, if detected
+- repo-specific notes from existing package scripts or manifests
+
+Never replace an existing `CLAUDE.md` without showing a diff and receiving approval.
+
+## Related
+
+- `config/project-stack-mappings.json` for stack-to-surface hints
+- `scripts/install-plan.js` for deterministic plan resolution
+- `scripts/install-apply.js` for dry-run and apply operations
+- `/ecc-guide` for interactive feature discovery before installing

package/seed/marketplaces/ecc/commands/projects.md

@@ -1,39 +1,39 @@
----
-name: projects
-description: List known projects and their instinct statistics
-command: true
----
-
-# Projects Command
-
-List project registry entries and per-project instinct/observation counts for continuous-learning-v2.
-
-## Implementation
-
-Run the instinct CLI using the plugin root path:
-
-```bash
-python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" projects
-```
-
-Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
-
-```bash
-python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py projects
-```
-
-## Usage
-
-```bash
-/projects
-```
-
-## What to Do
-
-1. Read `~/.claude/homunculus/projects.json`
-2. For each project, display:
-   - Project name, id, root, remote
-   - Personal and inherited instinct counts
-   - Observation event count
-   - Last seen timestamp
-3. Also display global instinct totals
+---
+name: projects
+description: List known projects and their instinct statistics
+command: true
+---
+
+# Projects Command
+
+List project registry entries and per-project instinct/observation counts for continuous-learning-v2.
+
+## Implementation
+
+Run the instinct CLI using the plugin root path:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" projects
+```
+
+Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
+
+```bash
+python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py projects
+```
+
+## Usage
+
+```bash
+/projects
+```
+
+## What to Do
+
+1. Read `~/.claude/homunculus/projects.json`
+2. For each project, display:
+   - Project name, id, root, remote
+   - Personal and inherited instinct counts
+   - Observation event count
+   - Last seen timestamp
+3. Also display global instinct totals