Add skip_ci_check composite action

[phelma]

Adds a skip_ci_check composite action that factors out the inline commit-message gate currently duplicated in every repo's main.yaml.

It takes the commit message as a required commit_message input (composite actions cannot reliably read the event payload across trigger types) and exposes a should_skip_ci output ("true"/"false") based on whether the message contains [no ci], [skip ci] or [ci skip]. The message is passed via an env var rather than interpolated into the script body.

This will be adopted by the CircleCI to GHA migration workflows so the skip-CI gate lives in one auditable place instead of being copy-pasted per repo.

README updated with a usage example. No tag changes — v1 is moved by a human after merge.

[phelma]

Superseded: the skip-ci-check job is being removed entirely — GitHub's native [skip ci] handling plus GITHUB_TOKEN push semantics already cover the loop-guard, so no shared action is needed.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a reusable composite GitHub Action to detect “skip CI” directives in commit messages and documents how to use it in workflows.

Changes:

• Introduces skip_ci_check composite action that outputs whether CI should be skipped based on commit message markers.
• Updates README to list the new action and provide a sample “gate job” configuration.

Reviewed changes

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

File	Description
skip_ci_check/action.yaml	Adds composite action that inspects commit messages and emits should_skip_ci.
README.md	Documents the new skip_ci_check action and provides a usage example.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.