Sync contribution-check workflow and agent from github/gh-aw (#171)

Author: Copilot

.github/agents/contribution-checker.agent.md

@@ -120,18 +120,18 @@ Hey @alice 👋 — thanks for working on the auth refactor! Here are a few thin
 
 If you'd like a hand, you can assign this prompt to your coding agent:
 
-````prompt
+` `` prompt
 Add unit tests for the rate-limiting middleware in src/auth/limiter.ts.
 Cover the following scenarios:
 1. Request under the limit — should pass through.
 2. Request at the limit — should return 429.
 3. Limit reset after window expires.
-````
+` ``
 ```
 
 ## Important
 
 - **Read-only** — NEVER write to the target repository. No comments, no labels, no interactions.
 - **Adapt to the project** — every CONTRIBUTING.md is different. Do not assume goals, boundaries, or labels that aren't in the document.
 - Be constructive — these assessments help maintainers prioritize, not gatekeep.
-- Be deterministic — apply the rules mechanically without hedging.
+- Be deterministic — apply the rules mechanically without hedging.

docs/contribution-check.md

@@ -24,11 +24,9 @@ You can trigger this workflow manually via workflow_dispatch or let it run on it
 
 The workflow uses a pre-filtering step to intelligently select PRs for evaluation. You can customize:
 
+- **Target repository**: Set a `TARGET_REPOSITORY` repository variable to check PRs in a different repository than where the workflow runs. By default, it checks the repository where the workflow is installed.
 - **Schedule frequency**: Change `every 4 hours` to your preferred interval
-- **PR filter logic**: Modify the skip conditions in the `github-script` step (e.g., which labels indicate trusted contributors, what constitutes a "small" PR)
-- **Batch size**: Adjust the `TARGET` constant (default: 10 PRs per run)
 - **Report format**: Customize the report layout rules in the main workflow prompt
-- **Skip labels**: Update `SKIP_LABELS` and `SMALL_LABELS` sets to match your repository's labeling conventions
 
 The workflow requires a `CONTRIBUTING.md` file (or `.github/CONTRIBUTING.md` or `docs/CONTRIBUTING.md`) to evaluate PRs against. If no contribution guidelines exist, PRs will be marked with `no-guidelines` quality.
 

workflows/contribution-check.md

@@ -170,4 +170,4 @@ If any subagent call failed (❓), also apply `outdated`.
 - **Write to `${{ github.repository }}`** — reports go here as issues.
 - **Use safe output tools for target repository interactions** — use `add-comment` and `add-labels` safe output tools to post comments and labels to PRs in the target repository `${{ env.TARGET_REPOSITORY }}`. Never use `gh` CLI or direct API calls for writes.
 - Close the previous report issue when creating a new one (`close-older-issues: true`).
-- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep.
+- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep.