dual-track-comms-hooks

Installs PreToolUse hooks enforcing terse-plus-collapsible formatting on GitHub, Linear, Slack, and Notion posts.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/christian-byrne/comfy-skills --skill dual-track-comms-hooks-christian-byrne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dual-track-comms-hooks
Source: https://github.com/christian-byrne/comfy-skills/tree/main/skills/dual-track-comms-hooks
Command: npx skills add https://github.com/christian-byrne/comfy-skills --skill dual-track-comms-hooks-christian-byrne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, flock, and includes scripts (resource) components.

What problem does it solve? Agents often post long, unstructured comments to GitHub, Linear, Slack, and Notion that bury the key takeaways. This Skill sets up mechanical enforcement of the dual-track comms format (terse top level plus a collapsible or threaded full-context section) so every outbound post is checked before it leaves the machine, without relying on the agent remembering the rule. ## Core Features & Use Cases - Adaptive environment discovery: Detects the user's agent harness (Claude Code, Amp, Codex, OpenCode) and posting tools (gh CLI, curl, MCP servers) before installing the matching interception mechanism. - Reference hook scripts: Bundled bash PreToolUse hooks check GitHub comments/reviews, Linear GraphQL commentCreate calls, Slack chat.postMessage payloads, and Notion MCP comments against length and collapsible-marker rules, with an override token and JSONL telemetry. - Advisory enforcement contract: Denies non-compliant posts with corrective guidance, fails open on unparseable input, and never polices long-form page content. - Use Case: A team lead asks their agent to set up the dual comms hooks; the Skill discovers they use Claude Code with the gh CLI and Notion MCP, copies the scripts to ~/.claude/hooks, registers the matchers in settings.json, and runs the bundled tests to verify allow, deny, and override behavior. ## Quick Start Ask your agent to install and configure the dual-track comms enforcement hooks for your current harness and posting tools.

Frequently Asked Questions about dual-track-comms-hooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce message formatting on GitHub comments made by an AI agent?▼

Register a Claude Code PreToolUse hook matching the Bash tool that runs the bundled dual-comms-external-posts.sh script. It pattern-matches gh pr comment, gh issue comment, and gh pr review commands and denies long bodies lacking a <details> collapsible block.

How do I set up PreToolUse hooks in Claude Code?▼

Copy the hook scripts to a stable directory such as ~/.claude/hooks, make them executable, then add a hooks.PreToolUse entry in ~/.claude/settings.json with a matcher (for example Bash or an MCP tool name) pointing at the script path.

Does this work with agent harnesses other than Claude Code?▼

Yes, the setup flow discovers the harness first and ports the same check contract to Amp plugins, OpenCode's tool.execute.before API, or a guidance-file fallback for Codex. The bundled bash scripts are the reference implementation for Claude Code only.

Can I bypass the hook for a legitimate long post?▼

Yes, include the token comms:exempt in the command or comment body and the hook allows the post while logging an overridden telemetry row. This escape hatch exists so genuine exceptions do not push users to disable the hook entirely.

Why does the hook allow my long Notion page edit but block my comment?▼

The hooks deliberately police only messages and comments, not documents. Notion page-content writes are long-form by nature and are not checked; only the comment-creation MCP tool is intercepted, since comments have no collapsible mechanism.