agent-harness-plugins copilot-instructions.md

GitHub Copilot Instructions

For full project conventions, see AGENTS.md in the repository root.

PR review

• Version bumps are selective: Only plugins with actual code changes get version bumps. Do not flag missing version bumps on unchanged plugins.
• PR descriptions may contain stale commit references: PR descriptions are often auto-generated from commit messages and may reference superseded commits. Do not flag discrepancies between PR description bullet points and the actual diff.
• Done plans are historical records: Files in docs/plans/done/ are completed plan documents preserved for reference. They may not match the final implementation. Do not flag discrepancies between done plan content and the actual codebase.

Skill and command files are AI agent prompts

Files under commands/ directories and SKILL.md files inside skills/ directories are prompts consumed by an AI agent, not user-facing shell scripts.

• Code blocks are agent instructions, not scripts: Code blocks in workflow steps are commands for the AI agent to execute and interpret; the agent reads command output directly and uses it programmatically. Do not suggest shell variable capture, output sanitization, or tr -d '\n' for commands whose output the agent handles natively.
• Branch-name placeholders are not injection vectors: Branch names in skill templates are always sanitized by prior slugification steps, and git itself rejects shell metacharacters in branch names. Do not flag these placeholders as shell injection vulnerabilities.
• Bare command names are documented placeholders: Bare command names like resolve-copilot-threads in code examples are documented placeholders for the script's quoted absolute path. A preamble in the "Script Setup" section explains this convention. Do not flag these as missing paths or broken commands.
• TOOL_BIN is a documented placeholder: In SKILL.md files and reference templates, TOOL_BIN is a placeholder that gets replaced with a tool-specific environment variable name (for example BOPCA_BIN, MY_TOOL_BIN) during execution. The naming convention (binary name uppercased, hyphens to underscores, suffixed with _BIN) is documented in each skill's workflow steps and in the SCRUT.md reference guide. Do not flag TOOL_BIN as a literal variable name or suggest replacing it with <TOOL>_BIN syntax.
• Pipeline-style directives are semantic, not literal: SKILL.md workflow steps are instructions for the agent, which reads command output and interprets it semantically. Directives like "filter SC3xxx codes from the output" mean the agent should ignore those codes when reporting results. Do not suggest adding shell filtering commands (grep -Ev, sed, awk) to skill instructions; the agent does not need pipeline-based filtering.
• "Tool Overview" tables show simplified commands: SKILL.md files contain a "Tool Overview" table that shows each tool's basic command form for quick reference. Full invocations with all flags (--exclude, --check, etc.) appear in the corresponding workflow sections below the table. Do not flag the table entries as incomplete or inconsistent with the workflow commands.
• Capitalized "NOT" in prohibitions is intentional emphasis: Some SKILL.md instructions use "Do NOT" instead of "Do not" for safety-critical prohibitions (for example, floating major version tags). The inconsistency with surrounding "Do not" phrasing is deliberate; the stronger emphasis signals higher-severity rules. Do not suggest normalizing these to sentence case.