@grimoire-cc/cli 0.8.0 → 0.9.0

package/packs/dotnet-pack/grimoire.json

@@ -3,50 +3,36 @@
   "version": "1.0.0",
   "agents": [
     {
-      "name": "grimoire:csharp-code-reviewer",
-      "path": "agents/gr.csharp-code-reviewer.md",
-      "description": "Expert C#/.NET code review specialist. Use immediately after writing or modifying C# code, or when explicitly requested to review C#/.NET code quality, security, performance, and best practices. ONLY reviews C# and .NET code - declines reviews of other languages."
+      "name": "grimoire.csharp-code-reviewer",
+      "path": "agents/grimoire.csharp-code-reviewer.md",
+      "description": "Expert C#/.NET code review specialist. Use immediately after writing or modifying C# code, or when explicitly requested to review C#/.NET code quality, security, performance, and best practices. ONLY reviews C# and .NET code - declines reviews of other languages.",
+      "version": "1.0.0"
     },
     {
-      "name": "grimoire:csharp-coder",
-      "path": "agents/gr.csharp-coder.md",
-      "description": "Implements C# code based on architectural decisions, predefined plans, or technical specifications. Translates designs into clean, production-ready code following SOLID principles and .NET conventions."
+      "name": "grimoire.csharp-coder",
+      "path": "agents/grimoire.csharp-coder.md",
+      "description": "Implements C# code based on architectural decisions, predefined plans, or technical specifications. Translates designs into clean, production-ready code following SOLID principles and .NET conventions.",
+      "version": "1.0.0"
     },
     {
-      "name": "grimoire:dotnet-architect",
-      "path": "agents/gr.dotnet-architect.md",
-      "description": "Write, review, or refactor C# code on the .NET platform following modern best practices. Implements new features using Clean Architecture, Domain-Driven Design (DDD), and Test-Driven Development (TDD). Designs domain entities, application services, API endpoints, and infrastructure components."
+      "name": "grimoire.dotnet-architect",
+      "path": "agents/grimoire.dotnet-architect.md",
+      "description": "Write, review, or refactor C# code on the .NET platform following modern best practices. Implements new features using Clean Architecture, Domain-Driven Design (DDD), and Test-Driven Development (TDD). Designs domain entities, application services, API endpoints, and infrastructure components.",
+      "version": "1.0.0"
     },
     {
-      "name": "grimoire:dotnet-unit-test-writer",
-      "path": "agents/gr.dotnet-unit-test-writer.md",
-      "description": "Expert .NET unit testing specialist for C#/.NET projects. Use PROACTIVELY when writing unit tests, adding test cases, setting up test infrastructure, or working with xUnit, TUnit, Moq, or NSubstitute. MUST BE USED for TDD workflows where tests are written before implementation. Defaults to xUnit (most universal), recommends TUnit for new .NET 8+ projects."
+      "name": "grimoire.dotnet-unit-test-writer",
+      "path": "agents/grimoire.dotnet-unit-test-writer.md",
+      "description": "Expert .NET unit testing specialist for C#/.NET projects. Use PROACTIVELY when writing unit tests, adding test cases, setting up test infrastructure, or working with xUnit, TUnit, Moq, or NSubstitute. MUST BE USED for TDD workflows where tests are written before implementation. Defaults to xUnit (most universal), recommends TUnit for new .NET 8+ projects.",
+      "version": "1.0.0"
     }
   ],
   "skills": [
     {
-      "name": "grimoire:dotnet-feature-workflow",
-      "path": "skills/gr.dotnet-feature-workflow",
+      "name": "grimoire.dotnet-feature-workflow",
+      "path": "skills/grimoire.dotnet-feature-workflow",
       "description": "Orchestrates end-to-end .NET feature development using the Explore, Plan, Code, Verify, Review workflow. Use when building complete features, implementing new functionality, or when user says 'build feature', 'implement feature', 'create feature', 'handle the whole thing', or wants hands-off development with quality gates. Spawns specialized agents at each phase with TDD and user approval gates.",
-      "triggers": {
-        "keywords": ["feature", "dotnet", "csharp", "scaffold", "endpoint"],
-        "file_extensions": [".cs", ".csproj", ".sln"],
-        "patterns": [
-          "build.*feature",
-          "implement.*feature",
-          "create.*feature",
-          "new.*feature",
-          "add.*feature",
-          "develop.*feature",
-          "csharp.*feature",
-          "handle.*whole",
-          "end.*to.*end",
-          "implement.*endpoint",
-          "build.*endpoint",
-          "add.*endpoint"
-        ],
-        "file_paths": ["**/*.csproj", "**/*.sln"]
-      }
+      "version": "1.0.0"
     }
   ]
 }

package/packs/dotnet-pack/skills/{gr.dotnet-feature-workflow → grimoire.dotnet-feature-workflow}/SKILL.md

@@ -1,8 +1,9 @@
 ---
-name: grimoire:dotnet-feature-workflow
+name: grimoire.dotnet-feature-workflow
 description: "Orchestrates end-to-end .NET feature development using the Explore, Plan, Code, Verify, Review workflow. Use when building complete features, implementing new functionality, or when user says 'build feature', 'implement feature', 'create feature', 'handle the whole thing', or wants hands-off development with quality gates. Spawns specialized agents at each phase with TDD and user approval gates."
-user_invocable: true
-disable-model-invocation: false
+user-invokable: true
+disable-model-invocation: true
+version: 1.0.0
 ---
 
 # .NET Feature Development Workflow

package/packs/essentials-pack/agents/{gr.fact-checker.md → grimoire.fact-checker.md}

@@ -1,8 +1,9 @@
 ---
-name: grimoire:fact-checker
-description: "Use this agent when you need to verify the accuracy of written content before publishing or sharing. Invoke when: (1) Drafting is complete and content contains factual claims like statistics, dates, technical specifications, or historical references; (2) Content is ready for final review before publishing; (3) Accuracy is critical for public-facing or decision-making materials. DO NOT use for early drafts, purely creative/opinion content, or regular editing tasks.\\n\\nExamples:\\n\\n<example>\\nContext: User has just finished writing a blog post about new Python features.\\n\\nuser: \"I just finished writing a blog post about Python 3.12's new features. Can you review it?\"\\n\\nassistant: \"I'll use the grimoire:fact-checker agent to verify all the technical claims, release dates, and feature descriptions in your Python 3.12 blog post before you publish it.\"\\n\\n<commentary>\\nSince the user has completed a blog post containing verifiable technical claims that need accuracy verification before publishing, use the Task tool to launch the grimoire:fact-checker agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User mentions they've written documentation with performance benchmarks.\\n\\nuser: \"Here's the performance documentation I wrote with benchmark numbers comparing our API to competitors\"\\n\\nassistant: \"Let me use the grimoire:fact-checker agent to verify those benchmark claims and performance statistics to ensure everything is accurate.\"\\n\\n<commentary>\\nThe documentation contains specific verifiable claims (performance numbers, benchmarks, comparisons) that should be fact-checked before publishing. Use the Task tool to launch the grimoire:fact-checker agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User has written an article with historical references and statistics.\\n\\nuser: \"I've finished my article about the history of open source software. It has dates, statistics, and some quotes from key figures.\"\\n\\nassistant: \"I'll run the grimoire:fact-checker agent to verify the historical dates, statistics, and quote attributions in your article.\"\\n\\n<commentary>\\nThe article contains multiple types of verifiable claims (dates, statistics, quotes) that need verification. Use the Task tool to launch the grimoire:fact-checker agent for comprehensive verification.\\n</commentary>\\n</example>"
+name: grimoire.fact-checker
+description: "Use this agent when you need to verify the accuracy of written content before publishing or sharing. Invoke when: (1) Drafting is complete and content contains factual claims like statistics, dates, technical specifications, or historical references; (2) Content is ready for final review before publishing; (3) Accuracy is critical for public-facing or decision-making materials. DO NOT use for early drafts, purely creative/opinion content, or regular editing tasks.\\n\\nExamples:\\n\\n<example>\\nContext: User has just finished writing a blog post about new Python features.\\n\\nuser: \"I just finished writing a blog post about Python 3.12's new features. Can you review it?\"\\n\\nassistant: \"I'll use the grimoire.fact-checker agent to verify all the technical claims, release dates, and feature descriptions in your Python 3.12 blog post before you publish it.\"\\n\\n<commentary>\\nSince the user has completed a blog post containing verifiable technical claims that need accuracy verification before publishing, use the Task tool to launch the grimoire.fact-checker agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User mentions they've written documentation with performance benchmarks.\\n\\nuser: \"Here's the performance documentation I wrote with benchmark numbers comparing our API to competitors\"\\n\\nassistant: \"Let me use the grimoire.fact-checker agent to verify those benchmark claims and performance statistics to ensure everything is accurate.\"\\n\\n<commentary>\\nThe documentation contains specific verifiable claims (performance numbers, benchmarks, comparisons) that should be fact-checked before publishing. Use the Task tool to launch the grimoire.fact-checker agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User has written an article with historical references and statistics.\\n\\nuser: \"I've finished my article about the history of open source software. It has dates, statistics, and some quotes from key figures.\"\\n\\nassistant: \"I'll run the grimoire.fact-checker agent to verify the historical dates, statistics, and quote attributions in your article.\"\\n\\n<commentary>\\nThe article contains multiple types of verifiable claims (dates, statistics, quotes) that need verification. Use the Task tool to launch the grimoire.fact-checker agent for comprehensive verification.\\n</commentary>\\n</example>"
 tools: Read, WebFetch, WebSearch
 model: inherit
+version: 1.0.0
 ---
 
 You are a meticulous fact-checking expert specializing in verifying claims, statements, and assertions across all types of written content including blog posts, articles, technical documentation, and other text-based materials. Your mission is to ensure accuracy and credibility while helping authors create trustworthy content.

package/packs/essentials-pack/grimoire.json

@@ -3,9 +3,10 @@
   "version": "1.0.0",
   "agents": [
     {
-      "name": "grimoire:fact-checker",
-      "path": "agents/gr.fact-checker.md",
-      "description": "Use this agent when you need to verify the accuracy of written content before publishing or sharing. Invoke when: (1) Drafting is complete and content contains factual claims like statistics, dates, technical specifications, or historical references; (2) Content is ready for final review before publishing; (3) Accuracy is critical for public-facing or decision-making materials."
+      "name": "grimoire.fact-checker",
+      "path": "agents/grimoire.fact-checker.md",
+      "description": "Use this agent when you need to verify the accuracy of written content before publishing or sharing. Invoke when: (1) Drafting is complete and content contains factual claims like statistics, dates, technical specifications, or historical references; (2) Content is ready for final review before publishing; (3) Accuracy is critical for public-facing or decision-making materials.",
+      "version": "1.0.0"
     }
   ],
   "skills": []

package/packs/meta-pack/grimoire.json

@@ -4,9 +4,10 @@
   "agents": [],
   "skills": [
     {
-      "name": "grimoire:context-file-guide",
-      "path": "skills/gr.context-file-guide",
+      "name": "grimoire.context-file-guide",
+      "path": "skills/grimoire.context-file-guide",
       "description": "Best practices for writing CLAUDE.md project context files. Use when creating, reviewing, or improving CLAUDE.md files for Claude Code projects.",
+      "version": "1.0.0",
       "triggers": {
         "keywords": [],
         "file_extensions": [],
@@ -23,9 +24,10 @@
       }
     },
     {
-      "name": "grimoire:readme-guide",
-      "path": "skills/gr.readme-guide",
+      "name": "grimoire.readme-guide",
+      "path": "skills/grimoire.readme-guide",
       "description": "Create and review README files following industry best practices. Use for writing new READMEs, improving existing ones, checking README quality, or adding badges.",
+      "version": "1.0.0",
       "triggers": {
         "keywords": [
           "readme"
@@ -46,9 +48,10 @@
       }
     },
     {
-      "name": "grimoire:skill-developer",
-      "path": "skills/gr.skill-developer",
+      "name": "grimoire.skill-developer",
+      "path": "skills/grimoire.skill-developer",
       "description": "Create and maintain custom skills for Claude Code following official Anthropic patterns. Use when creating new skills, updating existing skills, or organizing skill documentation.",
+      "version": "1.0.0",
       "triggers": {
         "keywords": [
           "skill-developer",

package/packs/meta-pack/skills/{gr.context-file-guide → grimoire.context-file-guide}/SKILL.md

@@ -1,6 +1,7 @@
 ---
-name: grimoire:context-file-guide
+name: grimoire.context-file-guide
 description: "Best practices for writing CLAUDE.md project context files. Use when creating, reviewing, or improving CLAUDE.md files for Claude Code projects."
+version: 1.0.0
 ---
 
 # CLAUDE.md Best Practices Guide

package/packs/meta-pack/skills/{gr.readme-guide → grimoire.readme-guide}/SKILL.md

@@ -1,8 +1,9 @@
 ---
-name: grimoire:readme-guide
+name: grimoire.readme-guide
 description: "Create and review README files following industry best practices. Use for writing new READMEs, improving existing ones, checking README quality, or adding badges. Triggers: readme, documentation, project docs, repository documentation, getting started guide, shields badges."
-user_invocable: true
+user-invokable: true
 disable-model-invocation: false
+version: 1.0.0
 ---
 
 # README Guide

package/packs/meta-pack/skills/{gr.skill-developer → grimoire.skill-developer}/SKILL.md

@@ -1,8 +1,9 @@
 ---
-name: grimoire:skill-developer
+name: grimoire.skill-developer
 description: Create and maintain custom skills for Claude Code following official Anthropic patterns. Use when creating new skills, updating existing skills, or organizing skill documentation.
-user_invocable: true
-disable-model-invocation: true
+user-invokable: true
+disable-model-invocation: false
+version: 1.0.0
 ---
 
 # Skill Developer

package/packs/ts-pack/grimoire.json

@@ -4,9 +4,10 @@
   "agents": [],
   "skills": [
     {
-      "name": "grimoire:modern-typescript",
-      "path": "skills/gr.modern-typescript",
+      "name": "grimoire.modern-typescript",
+      "path": "skills/grimoire.modern-typescript",
       "description": "Modern TypeScript best practices, patterns, and type system mastery for TS 5.7+. Use when writing TypeScript, reviewing TS code, designing types, configuring tsconfig, or asking about TypeScript patterns, generics, type safety, strict mode, idiomatic TypeScript, discriminated unions, branded types, or modern TS features.",
+      "version": "1.0.0",
       "triggers": {
         "keywords": ["typescript", "tsconfig", "satisfies", "narrowing", "readonly"],
         "file_extensions": [".ts", ".tsx", ".mts", ".cts"],

package/packs/ts-pack/skills/{gr.modern-typescript → grimoire.modern-typescript}/SKILL.md

@@ -1,6 +1,7 @@
 ---
-name: grimoire:modern-typescript
+name: grimoire.modern-typescript
 description: "Modern TypeScript best practices, patterns, and type system mastery for TS 5.7+. Use when writing TypeScript, reviewing TS code, designing types, configuring tsconfig, or asking about TypeScript patterns, generics, type safety, strict mode, idiomatic TypeScript, discriminated unions, branded types, or modern TS features."
+version: 1.0.0
 ---
 
 # Modern TypeScript