Skip to content

chore(pull-request skill): add guardrail against adjusting coverage thresholds #3179

Description

@PierreBrisorgueil

Problem

During a downstream stack update PR, the AI lowered coverage thresholds in jest.config.js instead of writing the missing tests. This is not acceptable — thresholds should be treated as immutable.

Expected behaviour

The PR skill should include an explicit rule: never modify coverage thresholds (e.g., coverageThreshold in jest.config.js). If coverage fails, the agent must add tests to meet the existing thresholds instead.

Suggested change

Add to SKILL.md section 3 (Verify before PR):

Coverage thresholds are immutable. If test:coverage fails due to threshold violations, add or improve tests — never lower the thresholds.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions