jasmeralia-work-hooks

Jira/Confluence/PagerDuty/Kibana workflow guard hooks, genericized from a specific employer's setup: any mention of a specific person's name or employer/repo-identifying detail has been stripped from comments and docstrings. The underlying detection logic is unchanged.

The Claude/Codex hooks.json matches the generic, commonly-published MCP server names (mcp-atlassian, pagerduty-mcp, kibana-mcp). If you have a second Atlassian/PagerDuty account behind a differently-named MCP server, add your own matcher entries locally (or in a project-level.claude/settings.json override) rather than expecting this plugin to guess your server naming.

• Claude Code:.claude-plugin/plugin.json + hooks/hooks.json.
• Codex: root plugin.json (Agent Plugins standard) reuses the same hooks/hooks.json.
• Cursor:.cursor-plugin/plugin.json + hooks/cursor-hooks.json, using Cursor's MCP: matcher convention with a regex alternation where a hook covers multiple tools. Best-effort: the exact MCP: naming (e.g. whether it's MCP:search or something more qualified for the Kibana tool) is not independently confirmed: verify against Cursor's actual MCP tool naming on first install and correct if it doesn't match.