ima-claude 2.20.0 → 2.26.0

package/plugins/ima-claude/skills/mcp-github/SKILL.md

@@ -11,77 +11,66 @@ description: >-
 
 # GitHub MCP - FOSS & Public Repository Management
 
-Use GitHub MCP tools for GitHub-hosted repositories. Falls back to the `gh` CLI when MCP tools aren't available.
+Use GitHub MCP tools for GitHub-hosted repositories. Falls back to `gh` CLI when MCP tools unavailable.
 
 ## Setup
 
-Requires `GITHUB_PERSONAL_ACCESS_TOKEN` in your environment:
-
 ```bash
 export GITHUB_PERSONAL_ACCESS_TOKEN=ghp_yourtoken
 ```
 
-The GitHub MCP server is HTTP-based at `api.githubcopilot.com`. Tools are prefixed `mcp__github__*` and are **dynamically served** — exact tool names may vary. If a tool call fails with "tool not found", fall back to the `gh` CLI table below.
+Server: `api.githubcopilot.com`. Tools prefixed `mcp__github__*`, dynamically served — exact names may vary. On "tool not found", fall back to `gh` CLI.
 
 ## Tool Catalog
 
-GitHub MCP tools map to GitHub REST API operations. Expected tools by category:
-
 **Repository**
 
-| Tool (expected) | Purpose |
-|-----------------|---------|
+| Tool | Purpose |
+|------|---------|
 | `mcp__github__search_repositories` | Find public repos by query |
-| `mcp__github__get_repository` | Get repo metadata (stars, forks, topics) |
-| `mcp__github__list_repository_contents` | List files/dirs in a repo |
-| `mcp__github__get_file_contents` | Read a file from any branch/commit |
-| `mcp__github__create_repository` | Create a new GitHub repo |
-| `mcp__github__fork_repository` | Fork a repo to your account |
+| `mcp__github__get_repository` | Repo metadata (stars, forks, topics) |
+| `mcp__github__list_repository_contents` | List files/dirs |
+| `mcp__github__get_file_contents` | Read file from any branch/commit |
+| `mcp__github__create_repository` | Create new GitHub repo |
+| `mcp__github__fork_repository` | Fork repo to your account |
 
 **Pull Requests**
 
-| Tool (expected) | Purpose |
-|-----------------|---------|
-| `mcp__github__list_pull_requests` | List PRs with filters (state, label, author) |
-| `mcp__github__get_pull_request` | Get PR details including diff metadata |
-| `mcp__github__create_pull_request` | Open a new PR |
+| Tool | Purpose |
+|------|---------|
+| `mcp__github__list_pull_requests` | List PRs (state, label, author filters) |
+| `mcp__github__get_pull_request` | PR details + diff metadata |
+| `mcp__github__create_pull_request` | Open new PR |
 | `mcp__github__update_pull_request` | Edit title, body, labels, assignees |
-| `mcp__github__merge_pull_request` | Merge a PR (merge, squash, or rebase) |
-| `mcp__github__list_pull_request_reviews` | Get review status |
-| `mcp__github__create_pull_request_review` | Submit a review (approve, request changes, comment) |
-| `mcp__github__list_pull_request_comments` | List inline code comments |
+| `mcp__github__merge_pull_request` | Merge (merge/squash/rebase) |
+| `mcp__github__list_pull_request_reviews` | Review status |
+| `mcp__github__create_pull_request_review` | Submit review (approve/request changes/comment) |
+| `mcp__github__list_pull_request_comments` | Inline code comments |
 
 **Issues**
 
-| Tool (expected) | Purpose |
-|-----------------|---------|
+| Tool | Purpose |
+|------|---------|
 | `mcp__github__list_issues` | List issues with filters |
-| `mcp__github__get_issue` | Get issue details and comments |
-| `mcp__github__create_issue` | Open a new issue |
+| `mcp__github__get_issue` | Issue details and comments |
+| `mcp__github__create_issue` | Open new issue |
 | `mcp__github__update_issue` | Edit title, body, state, assignees, labels |
-| `mcp__github__list_issue_comments` | Get all comments on an issue |
-| `mcp__github__add_issue_comment` | Post a comment on an issue |
-
-**Code & Files**
+| `mcp__github__list_issue_comments` | All comments on an issue |
+| `mcp__github__add_issue_comment` | Post comment |
 
-| Tool (expected) | Purpose |
-|-----------------|---------|
-| `mcp__github__search_code` | Search code across GitHub repos |
-| `mcp__github__create_or_update_file` | Commit a file change via API |
+**Code & Users**
 
-**Users & Orgs**
-
-| Tool (expected) | Purpose |
-|-----------------|---------|
-| `mcp__github__get_user` | Get GitHub user profile |
+| Tool | Purpose |
+|------|---------|
+| `mcp__github__search_code` | Search code across GitHub |
+| `mcp__github__create_or_update_file` | Commit file change via API |
+| `mcp__github__get_user` | GitHub user profile |
 | `mcp__github__search_users` | Find GitHub users |
 
 ## `gh` CLI Fallback
 
-When MCP tools aren't available or sufficient, use the `gh` CLI:
-
-| Operation | `gh` Command |
-|-----------|-------------|
+| Operation | Command |
+|-----------|---------|
 | Create PR | `gh pr create --title "..." --body "..."` |
 | List PRs | `gh pr list` |
 | View PR | `gh pr view 123` |
@@ -91,7 +80,6 @@ When MCP tools aren't available or sufficient, use the `gh` CLI:
 | Close issue | `gh issue close 123` |
 | View repo | `gh repo view owner/name` |
 | Fork repo | `gh repo fork owner/name` |
-| Clone fork | `gh repo clone owner/name` |
 | Search repos | `gh search repos "query"` |
 | Search code | `gh search code "query" --repo owner/name` |
 | View file | `gh api repos/owner/name/contents/path` |
@@ -99,102 +87,50 @@ When MCP tools aren't available or sufficient, use the `gh` CLI:
 ## Decision Logic
 
 ```
-Check git remote: git remote -v
-
-No remote configured?
-  → Local-only repo. Use git CLI directly.
+git remote -v
 
-Does the remote point to github.com?
-  → Yes: Use mcp__github__* tools
-      → MCP tools not available or responding?
-        → Use gh CLI as fallback
-  → No: Does it point to gitea.* / internal hostname?
-      → Yes: Use mcp__gitea__* tools (see mcp-gitea skill)
-      → Unknown: Check with the user
+No remote → git CLI only
+Remote = github.com → mcp__github__* (fallback: gh CLI)
+Remote = gitea.* / internal → mcp__gitea__* (see mcp-gitea skill)
+Unknown → ask user
 
-For local-only git operations (commit, diff, log, stash, branch):
-  → Always use git CLI directly — no MCP needed
+Local git ops (commit, diff, stash) → git CLI always
 ```
 
 ## Common Workflows
 
-### Create a PR for a FOSS Project
-
-```
-1. Confirm the remote is github.com:
-   git remote -v
-
-2. Create the PR:
-   mcp__github__create_pull_request
-     owner: "FLCCC"
-     repo:  "ima-claude"
-     title: "feat: add mcp-github skill"
-     body:  "## Summary\n..."
-     head:  "feat/mcp-github-skill"
-     base:  "main"
-```
-
-### Manage Issues
-
 ```
-# Open a bug report
+# Create PR
+mcp__github__create_pull_request
+  owner: "FLCCC"  repo: "ima-claude"
+  title: "feat: add mcp-github skill"
+  body: "## Summary\n..."
+  head: "feat/mcp-github-skill"  base: "main"
+
+# Create issue
 mcp__github__create_issue
-  owner: "FLCCC"
-  repo:  "ima-claude"
+  owner: "FLCCC"  repo: "ima-claude"
   title: "Bug: skill not loading"
-  body:  "Steps to reproduce..."
+  body: "Steps to reproduce..."
   labels: ["bug"]
 
-# Close with a comment
+# Close issue
 mcp__github__add_issue_comment
-  owner: "FLCCC"
-  repo:  "ima-claude"
-  issue_number: 42
-  body: "Fixed in v2.11.0"
-
+  owner: "FLCCC"  repo: "ima-claude"
+  issue_number: 42  body: "Fixed in v2.11.0"
 mcp__github__update_issue
-  owner: "FLCCC"
-  repo:  "ima-claude"
-  issue_number: 42
-  state: "closed"
-```
-
-### Search Public Repos
-
-```
-mcp__github__search_repositories
-  query: "claude code skills mcp"
-  sort: "stars"
-
-# Or via gh CLI:
-gh search repos "claude mcp skills" --sort stars --limit 10
-```
-
-### Review a PR
-
-```
-mcp__github__get_pull_request
-  owner: "FLCCC"
-  repo:  "ima-claude"
-  pull_number: 15
+  owner: "FLCCC"  repo: "ima-claude"
+  issue_number: 42  state: "closed"
 
+# Review PR
 mcp__github__create_pull_request_review
-  owner: "FLCCC"
-  repo:  "ima-claude"
-  pull_number: 15
-  event: "APPROVE"
-  body: "LGTM"
+  owner: "FLCCC"  repo: "ima-claude"
+  pull_number: 15  event: "APPROVE"  body: "LGTM"
 ```
 
 ## When NOT to Use
 
-- Internal Gitea repos — use `mcp-gitea` skill instead
-- Local git operations (commit, diff, stash) — use `git` CLI directly
-- Reading local files — use the Read tool, not the GitHub API
-- GitHub Actions configuration — edit files locally and push
-
-## Notes
-
-- GitHub MCP tools are **dynamically served** — exact names may differ. If a tool call fails with "tool not found", fall back to `gh` CLI.
-- The `gh` CLI is reliable and covers the majority of GitHub operations. MCP adds value for structured responses (search, bulk operations, code review workflows).
-- Always confirm the target remote (`git remote -v`) before deciding which tool to use.
+- Internal Gitea repos → use `mcp-gitea`
+- Local git operations → use `git` CLI
+- Reading local files → use Read tool
+- GitHub Actions config → edit locally and push

package/plugins/ima-claude/skills/mcp-memory/SKILL.md

@@ -3,180 +3,4 @@ name: "mcp-memory"
 description: "DEPRECATED — Use mcp-vestige instead. Vestige provides semantic search, spaced repetition, auto-dedup, and codebase awareness as a superset of Memory MCP. Triggers on: mcp-memory."
 ---
 
-> **DEPRECATED**: This skill is replaced by **mcp-vestige**. Vestige is a superset of Memory MCP with semantic search, FSRS-6 spaced repetition, prediction error gating, and codebase awareness. All proactive memory behaviors now route through Vestige.
->
-> This file is retained for reference during the transition period.
-
-# Memory MCP - Proactive Knowledge Graph (DEPRECATED)
-
-**You have access to a persistent knowledge graph that you rely on across all sessions.**
-
-Like Serena for code operations, Memory MCP is your system for preserving context. You use it **proactively** without being asked - checking for relevant context, storing decisions as they're made, and capturing learnings.
-
-## Proactive Behavior Rules
-
-**These are MUST behaviors, not suggestions:**
-
-### 1. Session Start: Check for Context
-When beginning work on any project, **automatically search memory** for relevant context:
-```
-mcp__memory__search_nodes query: "{project-name}"
-mcp__memory__open_nodes names: ["user-eric"]
-```
-This takes 2 seconds and prevents re-learning what you already know.
-
-### 2. During Work: Store Decisions As They Happen
-When ANY of these occur, **immediately store without being asked**:
-
-| Event | Action |
-|-------|--------|
-| User states a preference | Store to `user-eric` entity |
-| Architectural decision made | Create `decision-{topic}` entity |
-| Bug root cause identified | Create `bug-{description}` entity |
-| Pattern chosen over alternatives | Create `pattern-{name}` with rationale |
-| User corrects your approach | Update `user-eric` with the correction |
-| Configuration choice with rationale | Create `decision-{topic}` entity |
-
-**Recognition patterns** - store when you hear:
-- "I prefer..." / "I like..." / "I always..." / "I never..."
-- "Let's go with X because..." / "We chose X over Y"
-- "The reason this failed was..." / "Root cause:"
-- "From now on..." / "Going forward..."
-- "That's not how we do it" / "Actually, we..."
-
-### 3. Session End: Capture Learnings
-Before ending significant sessions, consider:
-- What decisions were made that should persist?
-- What did you learn about the user's preferences?
-- What patterns or approaches worked well?
-- What should you remember for next time?
-
-### 4. Before Asking Questions You Might Already Know
-Before asking "What framework do you use?" or "How do you prefer X?", **check memory first**:
-```
-mcp__memory__search_nodes query: "preference"
-mcp__memory__search_nodes query: "{topic}"
-```
-
-## Entity Structure
-
-### Core Entities (create these)
-
-**User Entity** (singleton - add observations, don't recreate):
-```
-name: "user-eric"
-entityType: "user"
-observations:
-  - "Prefers FP patterns over OOP"
-  - "Anti-over-engineering philosophy"
-  - "Wants minimal code comments"
-  - "Uses Quasar for Vue projects"
-```
-
-**Project Entities**:
-```
-name: "project-{name}"
-entityType: "project"
-observations:
-  - "Tech stack: X, Y, Z"
-  - "Key patterns: ..."
-  - "Gotchas: ..."
-```
-
-**Decision Entities**:
-```
-name: "decision-{topic}"
-entityType: "decision"
-observations:
-  - "Chose X over Y"
-  - "Rationale: ..."
-  - "Made: {date}"
-  - "Applies to: {scope}"
-```
-
-### Relations (create these to build the graph)
-```
-user-eric → owns → project-imanetwork
-project-imanetwork → follows → decision-fp-patterns
-decision-fp-patterns → supersedes → decision-old-oop-approach
-```
-
-## Available Tools
-
-| Tool | When to Use |
-|------|-------------|
-| `search_nodes` | **First** - before creating, before asking user |
-| `open_nodes` | Load specific known entities |
-| `create_entities` | New project, decision, pattern, bug |
-| `add_observations` | New facts about existing entity |
-| `create_relations` | Connect related entities |
-| `read_graph` | Debug / audit (use sparingly) |
-| `delete_*` | Cleanup outdated information |
-
-## Quick Patterns
-
-### Store a user preference (do this automatically)
-```
-mcp__memory__search_nodes query: "user-eric"
-# If exists:
-mcp__memory__add_observations
-  observations: [{"entityName": "user-eric", "contents": ["Prefers early returns over nested conditionals"]}]
-# If not exists:
-mcp__memory__create_entities
-  entities: [{"name": "user-eric", "entityType": "user", "observations": ["..."]}]
-```
-
-### Store a decision with rationale
-```
-mcp__memory__create_entities
-  entities: [{
-    "name": "decision-validators-at-registration",
-    "entityType": "decision",
-    "observations": [
-      "IMA Forms: validators defined at field registration, not validation time",
-      "Rationale: single source of truth, template IS the definition",
-      "Made: 2026-01-15",
-      "Supersedes: separate validation schema approach"
-    ]
-  }]
-mcp__memory__create_relations
-  relations: [{"from": "project-ima-forms", "to": "decision-validators-at-registration", "relationType": "follows"}]
-```
-
-### Check before asking
-```
-# Instead of asking "What's your code style preference?"
-mcp__memory__search_nodes query: "code style"
-mcp__memory__search_nodes query: "preference"
-# Only ask if nothing found
-```
-
-## What NOT to Store
-
-- Temporary debugging steps
-- One-off fixes unlikely to recur
-- Information already in project docs (CLAUDE.md, README)
-- Sensitive data (credentials, API keys)
-
-## Naming Conventions
-
-| Prefix | Use |
-|--------|-----|
-| `user-{name}` | User preferences, corrections |
-| `project-{name}` | Project context, tech stack |
-| `decision-{topic}` | Architectural choices with rationale |
-| `pattern-{name}` | Reusable code patterns |
-| `bug-{description}` | Root causes worth remembering |
-| `standard-{topic}` | Team/org standards |
-
-## The Key Insight
-
-**Serena works because it's wired into code operations automatically.**
-**Memory works when it's wired into decision-making automatically.**
-
-Don't wait to be asked. When context flows through the conversation that should persist:
-1. Recognize it
-2. Store it
-3. Mention briefly: "I've noted your preference for X"
-
-This builds a knowledge graph that makes every future session better.
+> **DEPRECATED**: Replaced by **mcp-vestige**. All proactive memory behaviors route through Vestige.