output-channel-contracts

Manage output channel configurations in AICodeReviewer for correct review result rendering.

1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/atframework/AICodeReviewer --skill output-channel-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: output-channel-contracts
Source: https://github.com/atframework/AICodeReviewer/tree/main/.agents/skills/output-channel-contracts
Command: npx skills add https://github.com/atframework/AICodeReviewer --skill output-channel-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage and audit output channel configurations in AICodeReviewer, ensuring that review results are rendered correctly across various notification channels.

Core Features & Use Cases

  • Output Channel Configuration Management: Configure and manage output channels for PR/MR comments, issues, bots, and other notification channels.
  • Policy Semantics Preservation: Ensure per-channel policy semantics are preserved during configuration changes.
  • Target Link Rendering: Accurately render target links for PR/MR, commit, push, P4 changelist, SVN revision, scheduled, and manual runs.
  • Documentation and Testing Alignment: Keep documentation, examples, and tests aligned with configuration changes.

Quick Start

Use the output-channel-contracts skill to review and update the output channel configuration for your AICodeReviewer instance.

Frequently Asked Questions about output-channel-contracts

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

FAQPage Schema
How do I configure output channels for AICodeReviewer notification targets?

Configure output channels in AICodeReviewer by managing settings for PR/MR comments, issues, and bots to ensure review results render correctly. This preserves per-channel policy semantics during configuration changes.

Why are target links not rendering correctly for SVN revision or P4 changelist runs?

Target links fail to render for SVN revision, P4 changelist, or push runs due to misconfigured output channels. Accurately rendering target links requires aligning channel configuration with the specific run type policies.

What is the best way to audit AICodeReviewer configuration changes for notification channels?

The best way to audit notification channel configurations is to review policy semantics and ensure documentation, examples, and tests remain aligned with the changes. This prevents broken review result rendering across channels.

Do I need to understand AICodeReviewer architecture to manage output channel contracts?

Yes, managing output channel contracts requires knowledge of AICodeReviewer's architecture and configuration. This understanding is necessary to preserve per-channel policy semantics and accurately render target links.

How do I keep documentation and tests aligned when modifying output channel configurations?

Keep documentation and tests aligned by auditing configuration changes and updating examples simultaneously. This ensures that policy semantics and target link rendering remain consistent across all notification channels.