• Strip CI skip markers from release commits before semver validation
• Support bracket and parenthesis variants of CI skip markers
• Add comprehensive test coverage for CI skip marker scenarios

Strip CI skip markers from version validation

• Enhanced isSemver function to strip CI skip markers before validation
• Added regex patterns to remove bracket-style markers like [skip ci], [ci skip], [skip-ci],
 [ci-skip]
• Added regex patterns to remove parenthesis-style markers like (skip ci), (ci skip),
 (skip-ci), (ci-skip)
• Maintains existing chore prefix removal logic while adding marker stripping

@commitlint/is-ignored/src/defaults.ts

Add CI skip marker test coverage

• Added test case for semver commits with bracket-style CI skip markers
• Added test case for semver commits with parenthesis-style CI skip markers
• Added test case for chore-prefixed commits with CI skip markers
• Tests cover all common CI skip marker variants (space and hyphen separated)

@commitlint/is-ignored/src/is-ignored.test.ts

Description

CI skip markers are stripped anywhere in the first line (not just as a trailing suffix), which can
turn some malformed release headers into a valid semver string and cause commitlint to skip linting
entirely. This widens the ignore condition beyond the PR’s stated goal of handling suffix markers on
release commits.

Code

@commitlint/is-ignored/src/defaults.ts[R11-15]

+	const stripped = firstLine
+		.replace(/^chore(\([^)]+\))?:/, "")
+		.replace(/\[(skip|ci)(-|\s)(ci|skip)\]/i, "")
+		.replace(/\((skip|ci)(-|\s)(ci|skip)\)/i, "")
+		.trim();

Evidence

isSemver removes CI markers via unanchored regex replacements, so a header like `chore: [skip ci]
1.2.3 becomes 1.2.3 after replacements and trim(), making semver.valid(...)` succeed. Since
lint() returns early with valid: true on any isIgnored(...) match, such a message would bypass
all rules.

@commitlint/is-ignored/src/defaults.ts[4-17]
@commitlint/is-ignored/src/is-ignored.ts[26-28]
@commitlint/lint/src/lint.ts[28-38]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`isSemver` currently strips `[skip ci]` / `(skip ci)` markers anywhere in the first line. Because `isIgnored()` causes `lint()` to skip all validation when `isSemver` returns true, this can ignore some malformed/oddly-formatted headers that become semver after stripping.

### Issue Context
The intent is to support semantic-release-style commit headers where CI skip markers are appended at the end (suffix), e.g. `chore(release): 2.3.3 [skip ci]`.

### Fix Focus Areas
- @commitlint/is-ignored/src/defaults.ts[11-16]

### Suggested approach
- After removing the optional `chore(...)?:` prefix, remove **one or more** trailing CI markers only.
- Consider a single regex that matches both bracket and paren forms and is anchored to end-of-line, e.g. remove `((\s*[\[(](?:skip|ci)(?:-|\s)(?:ci|skip)[\])])\s*)+$` (case-insensitive), then `trim()`.
- Add tests that ensure markers *before* the version are not treated as semver ignore cases (if that’s the desired policy).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The CI skip marker replacements are not global, so only the first occurrence of a marker is removed.
A semver commit containing repeated markers (e.g. 1.2.3 [skip ci] [skip ci]) may still fail semver
validation and not be ignored.

Code

@commitlint/is-ignored/src/defaults.ts[R12-15]

+		.replace(/^chore(\([^)]+\))?:/, "")
+		.replace(/\[(skip|ci)(-|\s)(ci|skip)\]/i, "")
+		.replace(/\((skip|ci)(-|\s)(ci|skip)\)/i, "")
+		.trim();

Evidence

Both regexes are missing the /g flag, so .replace(...) only removes the first match. The new
tests validate only single-marker cases, so this behavior is currently untested.

@commitlint/is-ignored/src/defaults.ts[11-15]
@commitlint/is-ignored/src/is-ignored.test.ts[127-143]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
CI skip marker `.replace()` calls are non-global, so repeated markers won’t be fully removed.

### Issue Context
While uncommon, repeated markers can happen via tooling or manual edits; failing to strip them defeats the purpose of normalizing the release commit header before semver validation.

### Fix Focus Areas
- @commitlint/is-ignored/src/defaults.ts[11-15]
- @commitlint/is-ignored/src/is-ignored.test.ts[127-143]

### Suggested approach
- Prefer the single-regex trailing-strip approach (anchored to `$`) that naturally handles repetition.
- If keeping the current approach, add `/g` to the regexes and add a test such as `expect(isIgnored("1.2.3 [skip ci] [skip ci]")).toBe(true)`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools