[MarkAlex1234]

Adds monorepo-affected-ci, a skill for making GitHub Actions in a monorepo run only the affected projects, including dependents of shared libraries, without the silent gaps hand-written path filters create.

Why it adds uplift over the model's defaults. These failure modes are common and easy to get wrong:

• on.paths filters that miss a shared library's dependents.
• Bare directories in paths that match nothing.
• Required checks that block merges forever when a path filter skips their workflow; the skill gives the always-run gate-job fix.
• An empty fromJSON matrix, which fails the job.
• The diff base for push on a new branch and for merge_group.

It includes a plan → matrix → gate workflow and a manifest-based algorithm for computing affected projects. It mentions dynamic-monorepo once, as an optional zero-config implementation, alongside Nx and Turborepo.

npm run skill:validate passes, and npm start regenerated docs/README.skills.md.

Disclosure: I maintain dynamic-monorepo. An AI agent prepared this PR.

[github-actions]

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier

• Label needs-review:HIGH flags a high contributor-risk signal

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Skill validation	✅ Passed	Passed · logs
Skill lint (vally)	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Contributor risk signal	🔧 Infrastructure failure	The contributor check succeeded but its result artifact was missing, unreadable, or for another commit · logs

Action needed

• 🔧 Contributor risk signal hit an automation problem that is not caused by your contribution. Comment /rerun-checks to retry; maintainers are notified if it keeps failing.

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s); an approval from a maintainer with admin or maintain permission
• The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 8e5e113 · gate run · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🔒 PR Risk Scan Results

Scanned 1 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	1
ℹ️ Info	0

Severity	Rule	File	Line	Match
🟠	package-exec-command	skills/monorepo-affected-ci/SKILL.md	75	npx github:Continuous-Actions/dynamic-monorepo audit

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔴 Contributor Reputation Check: HIGH risk

Check	Risk
Profile	HIGH
Credential audit	NONE

Maintainers: please review this contributor before merging.
See the workflow run for full details.
Automated check powered by AGT.

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	1
Agents	0
Total	1

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ monorepo-affected-ci (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed

Full linter output

### Linting skills/monorepo-affected-ci
✅ monorepo-affected-ci (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

[MarkAlex1234]

/request-review

[github-actions]

🙋 Added needs-reviewer. Reviewer routing is assigning a reviewer now.

[aaronpowell]

Thanks — useful pitfalls. Couple of review points:

• ci-ok must also require needs.plan.result == 'success'
• Ensure that it's clearly surfaced to the user that it runs npx github:Continuous-Actions/dynamic-monorepo so they are able to approve or reject, we're not just "blindly" installing stuff on their machine
• replace generic 'How to Compute Affected' with concrete gotchas and a merge_group example