Skip to content

feat(standards): require language instruction file links in Org Standards section#343

Open
don-petry wants to merge 3 commits into
mainfrom
feat/copilot-instructions-standard-language-links
Open

feat(standards): require language instruction file links in Org Standards section#343
don-petry wants to merge 3 commits into
mainfrom
feat/copilot-instructions-standard-language-links

Conversation

@don-petry

@don-petry don-petry commented May 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds an explicit requirement that repo-level copilot-instructions.md files MUST list each deployed language instruction file in ## Org Standards with a one-line scope description
  • Updates the template in copilot-instructions-standard.md to show the pattern with all six language files as examples
  • Adds copilot-instructions-missing-language-links to the compliance check table (for future audit enforcement)
  • Converts the prose language-file mention in the org-level copilot-instructions.md to the linked-list pattern, serving as the canonical example

Motivation

CodeRabbit flagged across the rollout PRs (#203, #241, #204, #181, #199, #357) that the ## Org Standards section didn't surface the language instruction files that were deployed alongside copilot-instructions.md. Contributors had no way to discover typescript.instructions.md etc. without browsing .github/instructions/. This change makes discoverability a standard requirement and closes the gap that caused those review comments.

Files changed

  • standards/copilot-instructions-standard.md — template updated, requirement added to intro + What to Include, compliance row added
  • .github/copilot-instructions.md — prose → linked list; serves as the live example of the pattern

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated development standards and templates to clarify code assistant configuration guidance across language-specific instruction files.

Review Change Stack

@don-petry don-petry requested a review from a team as a code owner May 22, 2026 12:56
Copilot AI review requested due to automatic review settings May 22, 2026 12:56
@coderabbitai

coderabbitai Bot commented May 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 12 minutes and 58 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 23d0e8a2-3e96-4949-9b41-6dcae45efd43

📥 Commits

Reviewing files that changed from the base of the PR and between 17f8932 and fa04b6b.

📒 Files selected for processing (2)
  • .github/copilot-instructions.md
  • standards/copilot-instructions-standard.md
📝 Walkthrough

Walkthrough

This PR updates Copilot instructions governance by expanding the standard template to require explicit listing of deployed language-specific instruction files in ## Org Standards sections with scope descriptions, adding a compliance check for missing language links, and updating the example file to demonstrate the canonical language instruction structure.

Changes

Copilot Instructions Standard and Language File Listing

Layer / File(s) Summary
Standard requirements for Org Standards section
standards/copilot-instructions-standard.md
The standard template now explicitly requires ## Org Standards to list every deployed language-specific instruction file under .github/instructions/ with one-line scope descriptions. Template block updated with canonical language links (TypeScript, JavaScript, Go, Shell, Python, Terraform) and instructions to list only deployed files or omit the block if none exist. "What to Include vs. What to Omit" rules clarified to require linking every deployed language file and prohibit unlisted files. New compliance warning copilot-instructions-missing-language-links added to detect unlisted files in .github/instructions/.
Example copilot-instructions.md demonstrating language file listing
``.github/copilot-instructions.md`
Updated example file's "Language-specific rules" section to enumerate the canonical language instruction files (TypeScript, JavaScript, Python, Go, Terraform, Shell) and clarify that language-specific rules are applied automatically via .github/instructions/.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: requiring language instruction file links in the Org Standards section of the standards template and the repo's copilot-instructions.md file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/copilot-instructions-standard-language-links

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the Copilot instructions and standards to improve the discoverability of language-specific instruction files. It mandates listing these files in the ## Org Standards section and introduces a new linting rule to verify their presence. Review feedback correctly identified that the relative links used in both the instructions file and the template were broken, as they incorrectly included the .github/ prefix while already residing within that directory.

Comment thread .github/copilot-instructions.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Copilot instruction-file standard to require that repositories explicitly link to any deployed language-specific instruction files from the ## Org Standards section, improving discoverability for contributors.

Changes:

  • Adds a MUST requirement to list each deployed .github/instructions/*.instructions.md file (with a one-line scope description) in repo-level copilot-instructions.md.
  • Updates the standards/copilot-instructions-standard.md template to demonstrate the linked-list pattern for all six language instruction files.
  • Adds a new (future) compliance check row: copilot-instructions-missing-language-links, and updates this repo’s .github/copilot-instructions.md to use the linked-list pattern.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
standards/copilot-instructions-standard.md Adds a normative requirement + template example for listing language instruction files; adds a compliance table row for missing links.
.github/copilot-instructions.md Converts the language-instruction prose reference into an explicit linked list intended as the canonical example.

Comment thread standards/copilot-instructions-standard.md Outdated
Comment thread .github/copilot-instructions.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 68e58688f7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/copilot-instructions.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1fc01cf7db

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread standards/copilot-instructions-standard.md Outdated
@donpetry-bot

donpetry-bot commented May 24, 2026

Copy link
Copy Markdown
Contributor
Superseded by automated re-review at a11fc5748f61961530a874552fc0c2a2133bd8f9 — click to expand prior review.

Review — fix requested (cycle 1/3)

The automated review identified the following issues. Please address each one:

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: LOW
Reviewed commit: 1fc01cf7db1957615fd0009cce8374ce74c5c456
Review mode: triage-approved (single reviewer)

Summary

This is a docs-only change that:

  1. Adds a normative requirement to standards/copilot-instructions-standard.md that every repo-level copilot-instructions.md MUST list each deployed .github/instructions/*.instructions.md file in ## Org Standards, with a one-line scope description.
  2. Updates the template in that standard to demonstrate the pattern with all six language files.
  3. Adds a new copilot-instructions-missing-language-links row to the compliance check table.
  4. Updates this repo's own .github/copilot-instructions.md to convert a prose mention into the linked-list pattern, serving as the canonical example.

Risk is LOW (docs-only, no code/CI changes), CI is fully green, and the underlying intent — improving discoverability of language instruction files — is sound. Triage routed this as low-risk and that classification is correct.

However, the triage tier did not surface the unresolved inline review comments. Confirming the change as-is would land a regression that defeats the PR's own purpose, so I'm escalating rather than approving.

Linked issue analysis

No linked issue (no closingIssuesReferences). The PR body describes the motivation (CodeRabbit feedback across rollout PRs #203, #241, #204, #181, #199, #357) clearly enough to evaluate against — no human escalation needed for context.

Findings

🛑 Blocking — broken relative links in both files (raised independently by gemini-code-assist, copilot-pull-request-reviewer, and chatgpt-codex-connector; not addressed in any follow-up commit — only an empty merge-from-main has landed since the initial push).

Both the live example in .github/copilot-instructions.md and the template in standards/copilot-instructions-standard.md use link targets of the form .github/instructions/<file>.instructions.md.

  • For .github/copilot-instructions.md, the file already lives in .github/, so a relative link .github/instructions/typescript.instructions.md resolves on GitHub to .github/.github/instructions/typescript.instructions.md — which does not exist. Every one of the six new links 404s when clicked. I confirmed by listing the repo at the PR head SHA: the instruction files are at .github/instructions/*.instructions.md, so the correct relative target from .github/copilot-instructions.md is instructions/<file>.instructions.md (or ./instructions/<file>.instructions.md).
  • The template block in standards/copilot-instructions-standard.md is explicitly intended to be copied verbatim into each repo's .github/copilot-instructions.md. So the same broken pattern propagates to every downstream rollout — every repo that adopts the template will ship 404 links and fail the new copilot-instructions-missing-language-links compliance check in spirit even if it nominally passes the presence check.

This is a correctness bug that directly defeats the stated discoverability improvement. Suggested fix (already provided as inline suggestions by gemini-code-assist on both files):

- [typescript.instructions.md](instructions/typescript.instructions.md) — …
- [javascript.instructions.md](instructions/javascript.instructions.md) — …
-

ℹ️ Non-blocking — consider tightening the compliance check description. The new table row reads:

.github/instructions/ contains files not listed in ## Org Standards

That phrasing makes the check sound like "presence" only. If the future linter that backs this rule can also validate link targets (i.e., that each listed link points to a file that actually exists at the relative path), it would catch exactly the bug above. Worth considering when the audit is implemented — not required for this PR.

CI status

All checks green (or appropriately skipped): Lint, ShellCheck, Secret scan (gitleaks), Agent Security Scan, AgentShield, CodeQL, SonarCloud, CodeRabbit status context, dependency-audit ecosystem detection (with language-specific audit jobs correctly skipped — this is a docs repo).


Reviewed automatically by the PR-review agent (single-reviewer mode: opus 4.7). Reply if you need a human review.

Additional tasks

  1. Resolve all unresolved review thread comments from other reviewers
  2. Ensure all CI checks pass after your changes
  3. Rebase on the target branch if behind
  4. Do NOT modify files unrelated to the findings above

The review cascade will automatically re-review after new commits are pushed.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17f8932b48

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/copilot-instructions.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/copilot-instructions.md:
- Around line 27-32: The canonical example (.github/copilot-instructions.md)
contains broken relative links that point to .github/.github/instructions/...;
update each referenced path (e.g., typescript.instructions.md,
javascript.instructions.md, python.instructions.md, go.instructions.md,
terraform.instructions.md, shell.instructions.md) so they use the correct
relative path from .github/copilot-instructions.md (i.e.,
.github/instructions/<file>.instructions.md should be replaced with
instructions/<file>.instructions.md or ./instructions/<file>.instructions.md)
ensuring the links resolve correctly when copied to downstream repos.

In `@standards/copilot-instructions-standard.md`:
- Line 214: Update the rule description for
`copilot-instructions-missing-language-links` to indicate a bidirectional check:
not only must `.github/instructions/` contain files listed in the `## Org
Standards` section, but each listed link must also resolve to an existing file
at the specified relative path; change the table cell text to something like
"Ensure files in `.github/instructions/` are listed in `## Org Standards` and
that each listed link resolves to the correct relative path (no broken links)."
Reference the `copilot-instructions-missing-language-links` rule, the
`.github/instructions/` directory, and the `## Org Standards` section when
making the edit.
- Around line 158-163: The relative links in the list (e.g.,
".github/instructions/typescript.instructions.md",
".github/instructions/javascript.instructions.md", etc.) are incorrect when this
file lives at .github/copilot-instructions.md and resolve to
".github/.github/..."; change those links to the correct relative path (for
example "./instructions/typescript.instructions.md" or
"instructions/typescript.instructions.md") for each entry ("TypeScript / TSX",
"JavaScript", "Go", "Shell", "Python", "Terraform") so they point to the real
files under .github/instructions/.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d3684388-6824-41e9-9742-2196d69f76df

📥 Commits

Reviewing files that changed from the base of the PR and between 21ea07e and 17f8932.

📒 Files selected for processing (2)
  • .github/copilot-instructions.md
  • standards/copilot-instructions-standard.md

Comment thread .github/copilot-instructions.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 47442f7fec

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread standards/copilot-instructions-standard.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e023f383a1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/copilot-instructions.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated
Comment thread standards/copilot-instructions-standard.md Outdated
@don-petry

Copy link
Copy Markdown
Contributor Author

@coderabbitai resolve

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

@don-petry

Copy link
Copy Markdown
Contributor Author

@coderabbitai resolve

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

coderabbitai[bot]
coderabbitai Bot previously approved these changes May 26, 2026
@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown
✅ Actions performed

Comments resolved and changes approved.

1 similar comment
@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown
✅ Actions performed

Comments resolved and changes approved.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cba203e615

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread standards/copilot-instructions-standard.md Outdated
coderabbitai[bot]
coderabbitai Bot previously approved these changes May 26, 2026
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

donpetry-bot
donpetry-bot previously approved these changes May 30, 2026

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: a11fc5748f61961530a874552fc0c2a2133bd8f9
Cascade: triage → deep (triage: haiku 4.5 → deep: sonnet 4.6 + duck: o4-mini → audit: opus 4.7)

Summary

Documentation-only PR that adds a discoverability requirement for language instruction files in Copilot standards. The broken relative-link issue flagged in the prior review cycle has been fixed (links now correctly use instructions/<file> rather than .github/instructions/<file>). The only remaining defect is five duplicate .dev-lead/ entries in .gitignore, which is a cosmetic artifact of repeated automated fix application and has zero functional impact. All CI checks pass, no security concerns.

Findings

  • MINOR: .gitignore contains 5 duplicate .dev-lead/ entries (lines 394-398) in addition to the pre-existing entry at line 393. Git silently ignores duplicate rules so there is no functional impact, but it is messy and appears to be an artifact of a bot applying the same fix multiple times. Worth cleaning up in a follow-up or squash before merge.
  • INFO: Relative links in .github/copilot-instructions.md now correctly use instructions/<file>.instructions.md (resolves to .github/instructions/ on GitHub). The template block in standards/copilot-instructions-standard.md uses the same relative form inside a code fence — correct for downstream copy-paste use. The broken-link issue raised in the prior deep review and by gemini-code-assist, copilot-pull-request-reviewer, and coderabbitai has been resolved.
  • INFO: PR is blocked on org-leads team review (REVIEW_REQUIRED). This is a human-gating requirement; the automated review approves the change but cannot fulfill the team-review gate.
  • INFO: New copilot-instructions-missing-language-links compliance row added to the check table. Current description only checks for presence (files in .github/instructions/ not listed in ## Org Standards). A future enhancement could also validate that listed links resolve to files that actually exist — this would have caught the original broken-link bug automatically.

Reviewed by the PR-review cascade (triage: haiku 4.5 → deep: sonnet 4.6 + duck: o4-mini → audit: opus 4.7). Reply if you need a human review.

donpetry-bot
donpetry-bot previously approved these changes May 30, 2026

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: a11fc5748f61961530a874552fc0c2a2133bd8f9
Review mode: triage-approved (single reviewer confirmation)

Summary

Confirming the triage-tier approval. This is a documentation-only change that (a) adds a requirement to standards/copilot-instructions-standard.md that the ## Org Standards section list every deployed language .instructions.md file with a one-line scope description, (b) updates the template block to demonstrate the pattern, (c) adds a new copilot-instructions-missing-language-links row to the compliance check table, and (d) converts the prose language-file mention in the org-level copilot-instructions.md to the linked-list pattern as a live example. The intent matches the PR description and motivation.

Linked issue analysis

No linked issue. PR body cites CodeRabbit feedback across rollout PRs (#203, #241, #204, #181, #199, #357) as motivation; that context is documented in the PR description rather than a tracked issue, which is acceptable for a small standards-doc change.

Findings

  • MINOR (carried forward from prior review, still unresolved): .gitignore contains six .dev-lead/ entries at the tail of the file (one pre-existing plus five duplicates added in this PR). Git deduplicates ignore rules so there is no functional impact, but the duplication appears to be an artifact of repeated automated fix-application and is unrelated to this PR's stated scope. Worth cleaning up in a follow-up commit or a squash-merge.
  • INFO: Relative links in both the org-level .github/copilot-instructions.md and the template inside standards/copilot-instructions-standard.md use the instructions/<file>.instructions.md form. For the org file this resolves correctly to .github/instructions/<file> on GitHub; for the template (inside a fenced code block, copied verbatim into target repos) the same form is also correct because target repos place the file at .github/copilot-instructions.md. Earlier broken-link concerns from gemini-code-assist, copilot-pull-request-reviewer, and coderabbitai are resolved.
  • INFO: The new copilot-instructions-missing-language-links compliance row only checks for presence (files in .github/instructions/ not listed in ## Org Standards). A future enhancement could additionally validate that listed links resolve to files that actually exist — that would have caught the original broken-link defect automatically. Not blocking.

CI status

All required checks green: Lint, CodeQL, Analyze, SonarCloud (×3), CodeRabbit, ShellCheck, Secret scan (gitleaks), Agent Security Scan, agent-shield/AgentShield, pr-auto-review, dev-lead/dispatch. Language-specific audit jobs (npm/pnpm/pip/cargo/govulncheck) skipped as expected for a docs-only change. Mergeable: CLEAN.


Reviewed automatically by the PR-review agent (single-reviewer mode). Reply if you need a human review.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

7 similar comments
@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@don-petry don-petry enabled auto-merge (squash) June 11, 2026 14:12
@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

2 similar comments
@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@donpetry-bot

Copy link
Copy Markdown
Contributor

@donpetry-bot I'm on it — starting a fresh review now. Results will appear in a few minutes.

@don-petry

Copy link
Copy Markdown
Contributor Author

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

@don-petry don-petry disabled auto-merge June 13, 2026 20:13
…ards section

Adds an explicit requirement that every repo-level copilot-instructions.md
MUST list the language-specific .instructions.md files deployed to
.github/instructions/, each with a one-line scope description, in the
## Org Standards section. Makes path-specific files discoverable without
requiring contributors to browse the directory.

Changes:
- standards/copilot-instructions-standard.md: update ## Org Standards
  template to show the language-link pattern, add to Required Sections
  intro, add to What to Include list, add copilot-instructions-missing-
  language-links compliance check row
- .github/copilot-instructions.md: convert prose language-file mention
  to linked list matching the new pattern (serves as the canonical example)
@don-petry don-petry force-pushed the feat/copilot-instructions-standard-language-links branch from e314466 to f109eab Compare June 13, 2026 20:16
@don-petry don-petry enabled auto-merge (squash) June 13, 2026 20:16
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@don-petry don-petry disabled auto-merge June 13, 2026 20:17
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry don-petry enabled auto-merge (squash) June 13, 2026 20:19
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@don-petry don-petry disabled auto-merge June 13, 2026 20:22
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@sonarqubecloud

Copy link
Copy Markdown

@don-petry don-petry enabled auto-merge (squash) June 13, 2026 20:25
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 0
- SonarCloud reported 0 new issues — quality gate passed
- CodeRabbit link concerns already resolved (confirmed by donpetry-bot)
- No Tier 1 blockers present
No action required. The PR is clean.
```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants