githits 0.11.3 → 0.11.4

package/skills/githits-mcp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: githits-mcp
-description: Use GitHits MCP as an OSS context layer when a task involves open-source packages, frameworks, SDKs, libraries, developer tools, package docs, repository source, examples, planning, research, vulnerabilities, changelogs, dependency graphs, or upgrade-review evidence. Prefer it before relying on model memory or generic web search for public OSS context.
+description: Use whenever invoking GitHits MCP tools for public OSS/package evidence: package, dependency, release, security, documentation, repository source/code search, or canonical examples. Load before any GitHits MCP tool call.
 ---
 
 # GitHits MCP
@@ -8,16 +8,10 @@ description: Use GitHits MCP as an OSS context layer when a task involves open-s
 Use GitHits when public OSS/package evidence would materially improve discovery, planning, research, implementation, debugging, or maintenance.
 
 When GitHits MCP tools are available, this skill already includes the stable
-quick-start guide below. Follow the guide and the selected tool descriptions for
-routing, scope, target syntax, output, safety, citations, and recovery.
-
-Current tool descriptions are authoritative over a stale installed skill
-snapshot. If any GitHits tool description exposed to the agent is marked
-`Experimental`, call `quick_start` before the first GitHits evidence tool to
-load runtime-specific guidance. Otherwise, call it only when needed to resolve a
-material mismatch between the loaded guide and the current descriptors.
-
-If GitHits MCP tools are unavailable but the `githits` CLI is installed, switch to the `githits-code` or `githits-package` skill and use its equivalent CLI commands. Do not treat missing MCP registration as evidence that GitHits lacks the requested content.
+quick-start guide below. Do not call `quick_start` when this skill is loaded;
+this rule applies to every GitHits tool. Follow the guide and the selected tool
+descriptions for routing, scope, target syntax, output, safety, citations, and
+recovery.
 
 ## Quick-start guide
 

package/skills/githits-onboarding/SKILL.md

@@ -1,10 +1,9 @@
 ---
 name: githits-onboarding
 description: >-
-  Set up GitHits from an agent session: detect supported coding tools, install
-  GitHits MCP configuration, start account sign-in/signup, verify auth, and
-  recover from setup issues. Use when the user asks to install, connect, set up,
-  sign up for, or start using GitHits.
+  Use when the user asks to install, connect, configure, sign in to, sign up
+  for, or start using GitHits. Covers agent detection, MCP and guidance
+  installation, authentication, verification, and setup recovery.
 compatibility: Requires shell access, internet access, and npx. Use a local githits binary only for explicit local/dev/pinned testing.
 ---
 

package/skills/githits-package/SKILL.md

@@ -1,11 +1,9 @@
 ---
 name: githits-package
 description: >-
-  Use GitHits CLI package-intelligence commands for package/dependency triage:
-  overview, latest version, license, repository health, vulnerabilities,
-  advisory history, dependency graphs, transitive provenance, changelogs,
-  release notes, and upgrade reviews. Activate for packages, dependencies,
-  versions, upgrades, CVEs, dependency footprints, or release changes.
+  Use whenever invoking the GitHits CLI for public package or dependency
+  evidence, including metadata, versions, licenses, vulnerabilities, dependency
+  graphs, changelogs, release notes, or upgrade reviews.
 compatibility: Requires shell access, internet access, and either a githits binary on PATH or npx.
 ---