📄 CodeRabbit inference engine (.agents/governance/interviews/security-interview.md)

Review infrastructure code changes including GitHub Actions workflows, git hooks, and Dockerfile for security vulnerabilities

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/metrics/baseline-report.md)

Infrastructure files (including .githooks/pre-commit) must receive security review before deployment

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml
• .github/labeler.yml

📄 CodeRabbit inference engine (.agents/metrics/dashboard-template.md)

Ensure infrastructure files in GitHub workflows directory are reviewed by agents with target rate of 100%

Implement full CodeRabbit enforcement for CI/CD workflow files in .github/workflows/ directory

.github/workflows/*: Detect files matching .github/workflows/* as infrastructure changes requiring specialist review from devops and security agents
GitHub Actions workflows must include an explicit permissions block with minimally privileged permissions
GitHub Actions workflows must not use pull_request_target trigger with actions/checkout action using pull request head SHA reference, as this creates a dangerous security pattern
GitHub Actions workflows requiring test reporting must explicitly grant checks: write permission for dorny/test-reporter compatibility
GitHub Actions workflows must avoid using overly permissive permissions: write-all and instead use explicit minimal permissions

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/security/infrastructure-file-patterns.md)

GitHub Actions workflow files (.github/workflows/*.yml and .github/workflows/*.yaml) should trigger security agent review due to critical security implications

Add security detection check to CI/CD pipelines to analyze staged files for infrastructure changes before implementation

.github/workflows/*.{yml,yaml}: Infrastructure files (.github/workflows/) require devops and security agent review before commit
Add pre-commit validation that fails on infrastructure files (.github/workflows/) lacking security review documentation
Infrastructure files must include a security impact analysis document before creation or modification
Retroactive security review is required for quick-fix changes to workflow files made without pre-commit review
Workflow files must validate that all required permissions are explicitly declared and justified

Keep workflow YAML files light and thin - MUST NOT put complex logic in workflow YAML files; use thin workflows with calls to external testable modules or skills

GitHub Actions workflows should remain thin and delegate complex logic to PowerShell modules rather than embedding bash-like commands in workflow YAML run blocks

.github/workflows/*.{yml,yaml}: Never use || true pattern without explicit error handling and ADR justification
Do not use || true error suppression in workflows without documenting rationale in an ADR

Use thin workflow pattern: minimize logic in YAML files, delegate complex operations to PowerShell modules

.github/workflows/*.{yml,yaml}: Use YAML heredoc with proper indentation for multi-line GitHub Actions values
Use GH_TOKEN for auto-authentication in GitHub Actions shell scripts
Use fixed-length lookbehinds for regex patterns in GitHub Actions
GitHub Actions outputs must be single-line format
Matrix jobs in GitHub Actions should use artifacts for output storage
Use environment variables for shell command interpolation in GitHub Actions to prevent injection vulnerabilities
Use verdict tokens for str...

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/utilities/security-detection/SKILL.md)

CI/CD workflow files (.github/workflows/*), git hooks (.githooks/*, .husky/*), and authentication code (**/Auth/**, **/Security/**) require security agent review (CRITICAL level)

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/analysis/pr41-issue-analysis.md)

.github/workflows/*.yml: Use dotnet-nunit reporter in dorny/test-reporter@v1 when Pester tests output NUnitXml format
Add explicit permissions block to GitHub Actions workflow jobs, specifying minimal required permissions (e.g., contents: read and checks: write for test reporting workflows)

.github/workflows/*.yml: Use minimal GitHub Actions permissions in CI workflows
Add workflow_dispatch trigger to GitHub Actions workflows for manual triggering capability
Add PowerShell-Yaml module installation step in CI workflows
Use ubuntu-latest for drift detection CI workflows for lighter weight execution
Add issue deduplication for drift alerts in GitHub Actions workflows
Use path filtering appropriately scoped in GitHub Actions workflows

CI/CD pipeline must include a drift-linting job that compares Claude agent content against generated VS Code and Copilot CLI variants on every PR modifying agent files

Create automated CI validation to detect absolute paths (Windows, macOS, Linux patterns) in markdown files with colored output, line numbers, and remediation steps

Configure concurrency groups in GitHub Actions workflows to prevent comment spam and race conditions when multiple commits trigger parallel workflow runs on the same PR

.github/workflows/*.yml: Remove silent || true error suppression from critical operations; instead track failures in arrays and provide summarized error reporting at workflow completion
Use minimal token scopes in GitHub Actions workflows: use repo scope for read-only operations, issues:write for issue modifications, and workflow permissions declarations following principle of least privilege

.github/workflows/*.yml: Store heredoc content in separate files instead of inline within YAML run: blocks to avoid YAML parsing errors when content lacks proper indentation
Use github.token (workflow's built-in token) for PR comments in GitHub Actions instead of service account PATs, as it automatically has write access t...

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/planning/prd-pre-pr-security-gate.md)

Detect files matching .github/**/*.yml as infrastructure changes requiring specialist review from devops and security agents

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml
• .github/labeler.yml

📄 CodeRabbit inference engine (.agents/retrospective/pr-feedback-remediation.md)

Use 'ubuntu-latest' for CI runner preference instead of 'windows-latest' for significantly faster performance, except for PowerShell Desktop or Windows-specific features

.github/workflows/**/*.{yml,yaml}: Workflows should be thin and contain only orchestration logic; all business logic (parsing, validation, formatting) must be extracted to PowerShell modules (.psm1)
Keep workflow YAML files to a maximum of 100 lines (orchestration only)
Do not parse complex strings (verdict, labels, etc.) in workflow YAML run: blocks; delegate to PowerShell modules
Do not validate business rules directly in workflow YAML; delegate to PowerShell modules
All PowerShell scripting for workflows must be PowerShell-only (no bash or other shell languages embedded in workflows)

.github/workflows/**/*.{yml,yaml}: PowerShell used consistently for label and milestone parsing in AI workflow (extract parsing logic to AIReviewCommon.psm1::Get-LabelsFromAIOutput rather than inline bash)
Use ::error:: GitHub Actions format for error output instead of echo or Write-Error to ensure errors are properly captured and cause workflow failure
Remove all '|| true' patterns and silent failure suppression in workflow steps - errors must be aggregated and reported explicitly using ::error:: format
Add token masking with ::add-mask:: before using secrets in workflow run steps to prevent accidental token leakage in logs
Replace secrets.BOT_PAT with github.token for issue and PR operations to minimize token privileges and reduce security attack surface
Document minimum required token scopes in workflow comments for each operation (e.g., 'repo' scope for issue edit and label application, 'read' scope for readonly operations)
Extract AI workflow parsing logic to testable PowerShell module functions (AIReviewCommon.psm1) rather than inline bash - enables unit testing in isolation and reduces regression risk

.github/workflows/**/*.{yml,yaml}: Use bash/PowerShell error collection pattern: initialize FAILED_...

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/skills/ci-runner-preference.md)

**/.github/workflows/*.{yml,yaml}: Use ubuntu-latest (or linux-latest) runners for GitHub Actions workflows instead of windows-latest for better CI/CD pipeline performance
Only use windows-latest runner when PowerShell Desktop (5.1) is required, Windows-specific features are needed, or testing Windows-only scenarios
Prefer PowerShell Core (pwsh) over PowerShell Desktop for GitHub Actions scripts to enable cross-platform compatibility on Linux runners

Workflows SHOULD be less than 100 lines, containing orchestration only. Business logic SHOULD be extracted to PowerShell modules (.psm1).

PowerShell workflow files must follow the thin-workflow pattern where orchestration logic stays in the workflow and business logic is extracted to reusable modules

Maintain consistent token scopes and authentication strategy throughout workflows; use the same token source for all related operations to avoid permission errors

**/.github/workflows/*.{yml,yaml}: Avoid code injection vulnerabilities by never directly interpolating unsanitized GitHub context variables (like ${{ github.event.issue.title }} or ${{ github.event.issue.body }}) into bash commands; instead save them to files using heredoc syntax and read them back
Use toJSON() to escape GitHub context variables when passing them to bash commands, or employ input validation before using variables in shell contexts
GitHub Actions workflows should request only the minimum necessary permissions (principle of least privilege) required for their operations

**/.github/workflows/*.{yml,yaml}: When ≥2 GitHub Actions workflows share logic, extract to composite action with parameterized inputs for reusability
GitHub Actions workflow files should include YAML syntax validation and actionlint checks in pre-commit configuration

**/.github/workflows/*.{yml,yaml}: Use artifacts instead of job outputs for passing data between matrix jobs in GitHub Actions workflows
Use environment variables for shell variable expans...

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/steering/security-practices.md)

Implement OWASP Top 10 prevention practices in GitHub Actions workflows

Use secure defaults and minimal exposure for security misconfiguration prevention

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

⚙️ CodeRabbit configuration file

.github/workflows/**: SECURITY-CRITICAL PATH - ASSERTIVE ENFORCEMENT
Review for: - Authentication and authorization (secrets handling, OIDC) - Credential exposure (env vars, git output, logs) - Injection vulnerabilities (command injection, script injection) - Race conditions (concurrent jobs, artifact operations) - Resource exhaustion (limits on runners, matrix expansions)
Flag: - Unquoted variables in shell commands - Direct use of user input in scripts - Missing error handling and early exit conditions - Hardcoded secrets or credentials - Unsafe use of 3rd party actions
DO NOT IGNORE any security-related findings on this path.

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/architecture/DESIGN-REVIEW-pr-60-remediation-architecture.md)

Use GitHub Actions workflow steps with PowerShell for JSON parsing and data manipulation; reserve bash only for simple npm install, git operations, and environment variable exports

Aggregate errors across workflow steps using error accumulation arrays and export failure summary via GITHUB_OUTPUT

.github/workflows/**/*.yml: GitHub Actions workflows orchestrating multiple agents should use matrix strategy with fail-fast: false to ensure all reviews complete
Use artifact passing (not job outputs) to transfer data between workflow jobs when using matrix strategy
Implement idempotency in workflow comment generation using comment markers to distinguish update vs create operations
Use skip optimization to check for docs-only changes before executing expensive AI review jobs
Add CI validation step to verify prompt templates include required output format markers before merging

.github/workflows/**/*.yml: Replace bash parsing with PowerShell functions in GitHub Actions workflows - use Get-LabelsFromAIOutput and Get-MilestoneFromAIOutput from AIReviewCommon.psm1 instead of bash grep/tr/xargs to prevent command injection (CWE-78) and word splitting vulnerabilities (CWE-20)
In GitHub Actions workflows parsing AI output, never use bash xargs, unquoted variable expansion, or for loops with simple string parsing - replace with PowerShell cmdlets that handle structured output safely
Verify PowerShell Core is available on GitHub Actions ubuntu-latest runner before using PowerShell in workflows

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/governance/PROJECT-CONSTRAINTS.md)

**/.github/workflows/**/*.{yml,yaml}: MUST NOT put business logic in workflow YAML files
SHOULD keep workflows under 100 lines (orchestration only)

Workflows must be thin and composed of testable, reusable modules

Follow Copilot follow-up PR naming convention: copilot/sub-pr-{original_pr_number} for branches targeting the original PR's base branch

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/planning/PR-60/001-pr-60-review-gap-analysis.md)

Use unique identifiers (e.g., run ID, timestamp) for temporary file paths in CI/CD workflows to prevent conflicts in concurrent runs on shared runners

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml
• .github/labeler.yml

📄 CodeRabbit inference engine (.agents/planning/PR-60/004-pr-60-implementation-review.md)

**/.github/workflows/**/*.yml: Replace bash label parsing in GitHub Actions workflows with PowerShell validation to prevent command injection via untrusted AI output
Validate all label strings against regex pattern '^[\w-.\s]{1,50}$' before applying to GitHub issues
Validate all category strings against regex pattern '^[\w-]{1,30}$' before using in workflow outputs
Validate all milestone strings against regex pattern '^[\w-.\s]{1,50}$' before assigning to issues
Use explicit error handling with informative error messages instead of '|| true' for GitHub CLI (gh) commands that should not fail silently
Keep '|| true' only for commands where empty/missing results are valid expected outcomes (e.g., grep with no matches, find with no results)
Verify GitHub CLI authentication status is successful before attempting API operations in CI workflows
Log validation rejections with details (invalid format, rejected label) for debugging label application failures
Provide detailed error messages in GitHub Actions workflow steps including context (what failed, why, what to check)
Use PowerShell 'Write-Host' with color output for structured workflow logging instead of plain echo statements
Use '|| true' in workflows only for commands where missing data is an expected valid state; document the reason in comments
Validate workflow inputs and outputs against strict regex patterns before using them in GitHub API commands

**/.github/workflows/**/*.yml: Use environment variables instead of direct ${{ }} template syntax in shell scripts to prevent shell injection attacks
Use artifacts instead of job outputs to pass data between matrix job legs, since outputs only expose one matrix leg
Prepare multi-line content via prior steps with GITHUB_OUTPUT heredoc syntax rather than attempting to execute shell commands in YAML with: inputs

Ensure GitHub workflow YAML files that use skip-validation jobs include a checkout step if equivalent reference implementations contain one

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/planning/PR-60/007-phase-1-detailed-schedule.md)

Use PowerShell-only code (no bash, Python, or shell scripts) with all workflow steps configured with 'shell: pwsh' per ADR-006

Use quoted heredoc (with 'EOF' delimiter) for safely handling github.event.pull_request.title and github.event.pull_request.body in bash env vars to prevent code injection

GitHub Actions workflows must use PowerShell functions from exported modules rather than inline bash parsing (grep/sed/tr) for consistent security and testability

In workflow comments, use explicit language about verdict behavior and consequences (e.g., 'should cause the check to FAIL (block merge)' rather than ambiguous phrasing)

**/.github/workflows/*.yml: Use PowerShell syntax (shell: pwsh) for GitHub workflow steps when handling untrusted AI output
Import PowerShell modules using correct relative path format (Import-Module .github/scripts/AIReviewCommon.psm1) in GitHub workflows to ensure module dependencies are properly resolved
Use PowerShell environment variables for all user input in GitHub workflows instead of direct bash variable interpolation to eliminate word-splitting vulnerabilities

Use $env:GITHUB_WORKSPACE with absolute paths instead of relative ./ prefix when importing PowerShell modules in GitHub Actions workflows

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/planning/pr-60-focused-plan.md)

Use sed with POSIX character classes instead of grep -P for regex patterns to ensure portability across Linux and macOS (grep -P is GNU-only)

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/planning/pr-60-security-review.md)

.github/{workflows,scripts}/**/*.{yml,yaml,sh}: Avoid leaking sensitive information or internal configuration details in error messages and workflow logs that could be visible to attackers. Use generic error messages in production and reserve detailed diagnostics for debug logs only.
Sanitize and validate all untrusted user input (such as GitHub event data like PR titles, issue bodies, commit messages) before using in shell commands, API calls, or other operations that could interpret special characters.
When updating GitHub comments in workflows, use idempotent markers (HTML comments with unique identifiers) in comment bodies to enable safe updates by specific comment ID rather than relying on comment position.

Enforce ADR-005 with pre-commit hook rejecting bash in .github/workflows/ and .github/scripts/ directories

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-18-ai-workflow-implementation.md)

AI automation in CI/CD requires verdict tokens (PASS/WARN/CRITICAL_FAIL) for deterministic bash parsing without AI interpretation

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-04-ai-workflow-debugging.md)

Avoid explicit gh auth login --with-token when GH_TOKEN environment variable is already set, as gh CLI automatically uses the env var and will fail with exit code 1

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-13-workflow-lessons.md)

Use composite actions to encapsulate reusable workflow steps (Node.js/npm/Copilot CLI setup, authentication, agent loading, verdict parsing)

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-13-workflow-lessons.md)

Convert single-job loops to multi-job matrix structures (detect → validate → aggregate) for parallel validation with artifact passing

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-34-pr-60-comment-response.md)

{.github/**/*.{sh,yml,yaml},**/*.sh}: Avoid gh auth login authentication patterns; use session-based authentication instead (reference Session 04 for implementation details)
Use secret masking for sensitive tokens like BOT_PAT in shell commands and CI/CD workflows

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml
• .github/labeler.yml

📄 CodeRabbit inference engine (.agents/qa/057-pr-222-import-module-standardization.md)

Standardize Import-Module paths to use $env:GITHUB_WORKSPACE variable instead of relative paths

Files:

• .github/workflows/label-issues.yml
• .github/workflows/label-pr.yml

📄 CodeRabbit inference engine (.agents/security/infrastructure-file-patterns.md)

PowerShell scripts in scripts directory (scripts/**/*.ps1) should trigger security agent review due to high security implications

Validation scripts belong in scripts/ directory; may duplicate to .agents/utilities/ for agent access

All scripts must avoid credential handling and should not store or process sensitive authentication information

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-15-cva-install-scripts.md)

Extract environment variations to .psd1 data files, keeping logic generic rather than hardcoding configuration in scripts

Convert PathInfo objects to string representations when passing to string-typed parameters to prevent type mismatch errors

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-15-documentation-gap.md)

Create module-specific README documentation for PowerShell scripts and modules, including parameter documentation and usage examples

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-15-install-scripts-session.md)

Use BeforeAll blocks for all variable initialization in Pester 5.x tests; avoid variable assignments outside BeforeAll during Discovery phase

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-15-instruction-files-gap.md)

User instruction files should be excluded from agent file copying during installation to prevent them from being treated as agent files

Use .Path property to extract string value from PathInfo objects returned by Resolve-Path in PowerShell (e.g., (Resolve-Path $Path).Path instead of Resolve-Path $Path)

PowerShell scripts should normalize output line endings (convert CRLF to LF) when output is intended to be processed by shell commands like grep to ensure cross-platform compatibility

Use -cmatch instead of -match when pattern requires case-sensitive matching in PowerShell validation scripts (e.g., EPIC vs epic for naming conventions)

**/*.ps1: In PowerShell script scope, use exit with explicit exit codes instead of return; return exits with code 0 regardless of boolean value
Document the bash-PowerShell exit code contract explicitly in PowerShell script comments: exit code 0 means success, non-zero means failure

When combining ShouldProcess with PassThru in PowerShell cmdlets: always provide explicit return value in else branch when ShouldProcess returns false

Before executing any PowerShell generation script, audit its code for alignment with known user requirements and identify dead/unused functions

**/*.ps1: Create regression tests for PowerShell scripts covering wildcard character detection, path resolution correctness, and edge cases when fixing path handling logic
In PowerShell, validate wildcard detection logic by distinguishing between literal wildcard characters (? and *) vs. actual wildcard patterns, using the -like operator correctly with character class escaping (e.g., *[?]* instead of *?*)

**/*.ps1: Before implementing features search for pre-existing test coverage
When tests pre-exist run them first to understand feature expectations
Use deep cloning to preserve source data integrity when transforming configurations
Use regex with exact match anchors (^...$) to prevent partial matches in configuration transformations
Up...

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-15-instruction-files-gap.md)

Verify that all files referenced in installer configuration (InstructionsFile, SourceDir, etc.) exist in their expected locations before release

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/roadmap/epic-agent-consolidation.md)

Build script must generate platform-specific YAML frontmatter for VS Code and Copilot CLI variants at build time

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/phase1-remediation-pr43.md)

Use relative paths only in documentation and configuration files; avoid absolute paths (e.g., C:\ on Windows) to prevent environment contamination and maintain cross-platform portability

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/steering/powershell-patterns.md)

**/*.{ps1,psm1}: Use approved verbs for PowerShell functions (Get-, Set-, New-, Remove-, etc.)
Implement parameter conventions and validation in PowerShell functions
Use proper error handling with ErrorActionPreference, try/catch blocks in PowerShell
Follow PowerShell pipeline usage and best practices for function design
Use comment-based help standards in PowerShell functions
Implement advanced function templates with CmdletBinding attribute
Use parameter validation attributes in PowerShell functions
Handle pipeline input properly in PowerShell cmdlets
Implement progress reporting for long-running PowerShell operations
Use proper configuration management patterns in PowerShell
Avoid using aliases in PowerShell scripts
Never suppress errors without proper error handling in PowerShell
Avoid hardcoded paths in PowerShell scripts

Use .claude/skills/github/ scripts for GitHub operations. NEVER use raw gh commands directly.

**/*.{ps1,psm1}: All PowerShell scripts (.ps1, .psm1) must include corresponding Pester test files (.Tests.ps1) with test coverage
PowerShell modules should use type safety, object pipelines, and structured error handling rather than string-based output

**/*.{ps1,psm1}: Use PowerShell regex pattern ^[a-zA-Z0-9][a-zA-Z0-9 _\-\.]{0,48}[a-zA-Z0-9]?$ for GitHub label validation to allow spaces in labels
All GitHub label validation must reject empty strings, accept single characters only if alphanumeric, reject newlines and tabs, enforce maximum 50 character limit per GitHub's specifications, and allow spaces in label names
Document all regex edge cases including empty string rejection, single character handling, newline/tab rejection, and character limit rationale in PowerShell code comments

MUST use PowerShell for all scripting (.ps1, .psm1)

**/*.{ps1,psm1}: Sanitize all values written to $env:GITHUB_OUTPUT by escaping newlines and special characters to prevent injection of arbitrary output variables
Quote label names in gh commands or...

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/analysis/003-session-protocol-skill-gate.md)

Validate skill availability before implementing GitHub operations - Check if .claude/skills/github/ directory exists and contains the required capability; list available GitHub skill scripts; read the skill-usage-mandatory memory; document available skills in session log; use existing skills if they exist rather than writing inline code

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/analysis/003-session-protocol-skill-gate.md)

NEVER use raw gh commands (like gh pr view, gh issue create, gh api) when a Claude skill exists for that functionality - Always use the tested skill scripts from .claude/skills/github/ instead of writing inline commands

**/*.{ps1,yml,yaml}: Use atomic gh label create $label --force operation instead of separate check + create steps to prevent TOCTOU race conditions
Implement all 4 mandatory Phase 1 security hardening conditions (label creation atomicity, auth check always-run, GITHUB_OUTPUT sanitization, debug file path randomization) before merge approval

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/analysis/004-pr-60-gap-coverage-validation.md)

Add explicit exit code checks for npm and GitHub CLI commands instead of using || true error suppression patterns

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/analysis/004-pr-60-gap-coverage-validation.md)

Generate unique temporary directories for each workflow run using timestamped or UUID-based naming to prevent directory collision

Ensure authentication checks always run and are not skipped by conditional logic in diagnostics mode - remove or restructure conditions that bypass authentication

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/planning/PR-60/006-agent-validation-sign-offs.md)

Align all PowerShell implementations with ADR-005 (PowerShell-only requirement) and ADR-006 (thin workflows principle) to maintain architecture coherence

Add rate limiting for label operations to prevent DoS of GitHub API quota by capping the maximum number of labels per issue

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/planning/PR-60/007-phase-1-detailed-schedule.md)

Verify exit code after each critical command (gh issue edit, npm install) in PowerShell workflows and scripts

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/planning/PR-60/007-phase-1-detailed-schedule.md)

Remove or justify all '|| true' patterns in PowerShell scripts and workflows to prevent silent failures

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/planning/PR-60/007-phase-1-detailed-schedule.md)

Replace 'exit 1' with 'throw' statements in PowerShell modules and scripts for proper exception handling

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-18-serena-memory-reference-migration.md)

Search entire codebase for pattern before migration to identify all references

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/security/SR-PR60-implementation-review.md)

Use unique, secured temporary file paths with random identifiers and cleanup logic instead of hardcoded predictable paths like /tmp/categorize-output.txt

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-21-check-skill-exists.md)

PowerShell scripts must support -Operation, -Action, and -ListAvailable parameters with ValidateSet constraint for valid operations

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-19-skill-extraction-summary.md)

Use identical syntax for all instances when migrating patterns to maintain consistency

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-20-pr-94-acknowledgment-failure.md)

PowerShell script failure requires immediate gh CLI fallback attempt (dual-path tooling for GitHub operations)

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/sessions/2025-12-20-session-43-qa-validation-pr147.md)

Use regex patterns with single-line mode flag (?s) for multi-line matching in YAML comment extraction

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/critique/047-pr-212-retrospective-critique.md)

Use ([pattern])? instead of [pattern]? for optional trailing groups in regex to ensure correct optional behavior and prevent special character bypass

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/retrospective/2025-12-20-pr-212-comment-response.md)

Use atomic optional groups ([pattern])?$ instead of [pattern]?$ for optional trailing characters in regex validation to prevent special character bypass

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/sessions/2025-12-20-session-01.md)

Verify regex validation patterns in security remediation code

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/sessions/2025-12-21-session-53-pr212-security-continuation.md)

Transform validation error messages into 5-word activation prompts that trigger correct behavior

Use gh api --paginate flag when fetching sweep jobs to handle pagination in GitHub CLI commands

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/sessions/2025-12-21-session-57-pr-222-review-response.md)

Include the -Force flag when using Import-Module to ensure module reload and prevent stale module state

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/HANDOFF.md)

Use PowerShell only for script implementations, avoiding bash and Python (ADR-005 compliance)

Files:

• scripts/Invoke-BatchPRReview.ps1

📄 CodeRabbit inference engine (.agents/pr-comments/PR-225/comments.md)

Clarify optional skill dependencies in command documentation, specifically marking /pr-comment-responder as optional with separate installation guidance in .claude/commands/pr-review.md

Files:

• .claude/commands/pr-review.md

📄 CodeRabbit inference engine (.agents/governance/interview-response-template.md)

Primary deliverables from agents should be saved to .agents/[category]/[pattern].md with naming convention [PREFIX]-NNN-[description].md

Single-source agent files should use frontmatter markers to delineate platform-specific sections for VS Code and Copilot CLI variants

Maintain artifact synchronization markers in tracking files (.md) with status indicators ([COMPLETE], [RESOLVED], [VERIFIED]) and timestamps to document completion and verification of work

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/critique/001-agent-templating-critique.md)

For agent platform files, evaluate whether near-identical variants (99%+ overlap) can be consolidated with conditional configuration rather than maintaining separate files

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)

.agents/**/*.md: Use PREFIX-NNN naming convention (e.g., EPIC-001, CRITIQUE-001) for sequenced artifacts and type-prefixed naming (e.g., prd-, tasks-) for non-sequenced artifacts
Normalize all file paths in markdown documents to be repository-relative before committing, removing absolute machine-specific paths

.agents/**/*.md: Session logs and documentation must include Phase checklist verification (Phase 1-3 protocol compliance including agent activation, instruction reading, handoff file updates, and session logging)
Session logs must document Session ID, date, agent name, and branch information in a standardized header format

All artifact files in .agents/ must be in Markdown format

Document analysis recommendations with specific rationale when adding new governance documents like PROJECT-CONSTRAINTS.md

Maintain debugging skills documentation in .agents/ directory

Document implementation notes explaining deviations from user prompts or decisions made during development (e.g., using plural form for directory names)

Run markdown lint on all generated artifacts before completing a session

Run markdown lint validation (0 errors expected) before committing documentation files in the .agents directory

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/SESSION-END-PROMPT.md)

Create retrospective document at .agents/retrospective/YYYY-MM-DD-session-NN.md with analysis of emerging patterns, skills to extract, learnings, and discovered risks

Retrospective analysis documents must include Phases 0-5 (Data Gathering, Generate Insights, Diagnosis, Decide What to Do, Learning Extraction, Close)

Retrospective documents MUST include atomicity validation table, deduplication analysis section, and clear skills extraction summary with impact metrics (scored 1-10)

Retrospective analysis files should document outcomes, patterns, and learnings from completed sessions while maintaining clarity about tool usage patterns discovered

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/governance/naming-conventions.md)

Retrospective artifacts should use the pattern YYYY-MM-DD-[kebab-case-topic].md with ISO 8601 date format, located in .agents/retrospective/ (e.g., 2025-01-15-authentication-sprint.md)

Retrospective artifacts must follow naming pattern YYYY-MM-DD-topic.md

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/sessions/2025-12-18-session-10-hyper-critical-retrospective.md)

Document failures and fixes in retrospective analysis files

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

⚙️ CodeRabbit configuration file

Agent configuration files. Only flag security issues or broken cross-references. Ignore style, formatting, and structure.

Files:

• .agents/retrospective/2025-12-22-pr-226-premature-merge-failure.md

📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)

Update memory/knowledge base snapshots when refined estimates or critical data diverges from previously stored values by more than 10%

.serena/memories/**/*.md: Skill memory files MUST include atomicity scores (>85% threshold required for persistence), evidence citations with specific session numbers, and SMART validation criteria (Specific, Measurable, Actionable, Relevant, Time-bound)
Skill deduplication analysis MUST be performed with similarity scoring (0-100%) before persistence, comparing new skills against existing memories and documenting the decision (ADD, UPDATE, or MERGE)
All skill memory entries MUST include source reference, validation count (number of times applied), and cross-references to related skills in other memory files

.serena/memories/**/*.md: Atomic memory files must contain focused, high-relevance content to minimize token waste during read operations; avoid consolidating multiple skills into single library files
Memory files and index statements must be designed for human readability and agent pattern recognition; avoid relying on unverified internal mechanisms like word frequency matching

Capture user insights about token efficiency and activation vocabulary in the .serena/memories/ directory for future reference

Document workflow pattern requirements (such as dorny/paths-filter checkout dependencies) in serialized memory files for future reference

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/analysis/004-check-skill-exists-tool.md)

Memory files documenting skill usage requirements (e.g., skill-usage-mandatory.md) must be kept synchronized with actual Check-SkillExists.ps1 tool interface and available skills

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/analysis/005-semantic-slug-protocol-analysis.md)

Use semantic slug naming convention for memory files instead of numeric IDs, following the pattern skill-{technology}-{technique}.md (e.g., skill-git-squash-merge-clean-history.md)

Consolidate atomic skill files into domain libraries (e.g., merge multiple skill-react-*.md files into a single context-react-development-standards.md) with a target of 15-20 domain libraries instead of 65+ individual files

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/analysis/005-semantic-slug-protocol-analysis.md)

Use prefix taxonomy for memory files: adr- for Architecture Decision Records, context- for domain knowledge libraries, pattern- for reusable solution patterns, and skill- for how-to guides

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/analysis/005-semantic-slug-protocol-analysis.md)

Use descriptive slugs in memory file names that include the technology, domain, and specific technique to enable LLM semantic matching (e.g., skill-pester-test-isolation-pattern.md rather than Skill-PowerShell-004.md)

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/analysis/005-semantic-slug-protocol-analysis.md)

Enforce semantic slug distinctiveness to prevent near-duplicate file names within the same domain (e.g., avoid both skill-git-rebase.md and skill-git-interactive-rebase.md)

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/critique/050-token-efficiency-principle-critique.md)

Use sequential numbering and collision prevention patterns for memory file naming to enforce skill lifecycle states and governance

.serena/memories/skill-*.md: Skill memory files in .serena/memories/ with names matching skill-* or skills-* pattern are subject to retrieval tracking and cold skill identification
Cold skill identification must exclude newly created skills (created less than threshold days ago, default 30 days) when reporting unused skills

.serena/memories/skill-*.md: Enforce skill ID naming convention: Skill-{Domain}-{Number} where Domain is CamelCase, Number is 3-digit zero-padded (001-999), and skill IDs must be globally unique
Reserve skill ID numbers 001-099 per domain for foundational skills; higher numbers (100+) are available for advanced or specialized skills

.serena/memories/skill-*.md: Extract skills from retrospectives with atomicity score >= 85%, persisting to .serena/memories/ with Skill-{Domain}-{Number} naming convention
Use structured skill ID naming: Skill-{Domain}-{Number} with CamelCase domain and 3-digit zero-padded number (e.g., Skill-Analysis-001)

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/planning/PRD-skills-index-registry.md)

.serena/memories/skill*.md: Include activation vocabulary (5 words) in both skill file names and index statements to increase LLM association patterns and selection probability during skill discovery
Preserve all deprecated skill files (do NOT delete); link them in the index's Deprecated Skills section to prevent confusion when old references appear in historical documents

.serena/memories/skill*.md: Skill files must be renamed from numeric ID pattern (skill-domain-NNN) to semantic slug pattern (skill-domain-semantic-slug.md)
Verify all skill file migrations with content hash verification to ensure no data loss or corruption
Test Serena MCP integration operations (read_memory, list_memories, write_memory, edit_memory) with new semantic slug names to ensure compatibility

Maintain skill lifecycle states with transitions: Draft → Active → Deprecated, with replacement references for deprecated skills

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/sessions/2025-12-20-session-22.md)

Memory file names and index statements MUST contain dense, high-signal keywords because agents select memories based on word frequency matching

**/.serena/memories/**/*.md: Use semantic slugs for memory file naming instead of numeric IDs (e.g., skill-git-squash-merge-clean-history.md instead of Skill-Git-004.md)
Adopt prefix taxonomy for memory files: adr-[number]-[slug].md for architectural decisions, context-[domain]-[topic].md for domain knowledge, pattern-[problem]-[solution].md for recurring solutions, skill-[technology]-[technique].md for how-to guides

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/sessions/2025-12-20-session-48-semantic-slug-orchestration.md)

Commit all changes including .serena/memories files as part of session completion

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

📄 CodeRabbit inference engine (.agents/sessions/2025-12-20-session-38-pr-94-review.md)

Document discovered skills from retrospectives or code reviews with atomicity scores and evidence references in the skillbook

Files:

• .serena/memories/skill-autonomous-execution-guardrails.md

[style] ~39-~39: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 1861 characters long)
Context: ... ``` Verify: PR exists, is open (state != MERGED, CLOSED), targets current repo....

(EN_EXCESSIVE_EXCLAMATION)

[uncategorized] ~63-~63: The official name of this software platform is spelled with a capital “H”.
Context: ...--------| | skill-usage-mandatory | Use .claude/skills/github/ scripts | Used raw gh api commands ...

(GITHUB)