mirror of https://github.com/getsentry/sentry-for-ai.git synced 2026-09-14 14:28:22 +08:00

Files

T

History

Evan Purkhiser 765cca4683 feat(grok): place plugin.json at .grok-plugin/plugin.json in dist (#175 )

The xAI plugin marketplace scanner (generate-plugin-index.py) resolves
plugin manifests from MANIFEST_PATHS = ['.grok-plugin/plugin.json',
'.claude-plugin/plugin.json']. With the manifest at the repo root it was
silently ignored — components were still discovered via default paths, but
any manifest-level overrides (e.g. logo) would not have been picked up.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-15 13:06:52 -04:00

build.sh

feat(grok): place plugin.json at .grok-plugin/plugin.json in dist (#175 )

2026-06-15 13:06:52 -04:00

marketplace.json

feat(dist): build and publish per-agent plugin distributions (#158 )

2026-06-12 13:39:38 -04:00

plugin.json

feat(dist): build and publish per-agent plugin distributions (#158 )

2026-06-12 13:39:38 -04:00

README.md

feat(dist): build and publish per-agent plugin distributions (#158 )

2026-06-12 13:39:38 -04:00

validate.sh

feat(grok): place plugin.json at .grok-plugin/plugin.json in dist (#175 )

2026-06-15 13:06:52 -04:00

README.md

Sentry for Grok

The Sentry plugin for Grok. It teaches Grok how to use Sentry: SDK setup wizards for any platform, production issue debugging via the Sentry MCP server, code review with Sentry context, and monitoring configuration.

Important

This repository is generated. It is built from getsentry/sentry-for-ai and includes every skill in that library. Do not edit files here; make changes in that repository and they will be rebuilt into this one.

Install

grok plugin install getsentry/plugin-grok --trust

What's included

The full Sentry skill library (SDK setup wizards, debugging and code-review workflows, feature setup).
The /seer command for natural-language Sentry queries.
The hosted Sentry MCP server for querying your Sentry environment.

A few router skills are always available; the rest are hidden behind them with disable-model-invocation and load on demand, so they do not crowd the model's context.