[stphschne]

This PR fixes #2667

Implemented changes:

• Change 1: Added check-ai-attribution.sh to create error for AI-commits.
• Change 2: Added new hook: commit-msg.
• Change 3: Added new job in build-pr.yml(name: Check commit messages).
• Change 4: Added new message in install-hooks.sh to inform about ai-attribution blockage.

---

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

1.Open Git Bash
2.Run ./install-hooks.sh. commit-msg and check-ai-attribution should be active.
3.Run following tests:
1.cat > /tmp/ai-msg.txt <<EOF
#2667: Add commit check

Co-authored-by: Copilot copilot@github.com
EOF

git-hooks/check-ai-attribution.sh /tmp/ai-msg.txt
echo $?
Error expected. Should return 1.
2.cat > /tmp/human-msg.txt <<EOF
#2667: Add commit check

Co-authored-by: Max Mustermann max@example.com
EOF

git-hooks/check-ai-attribution.sh /tmp/human-msg.txt
echo $?
Should return 0.

3.cat > /tmp/generated-msg.txt <<EOF
#2591: Add commit check

Generated with Claude Code
EOF

git-hooks/check-ai-attribution.sh /tmp/generated-msg.txt
echo $?
Error expected. Should return 1.
4.Run following command:
git config --local core.hooksPath

Should return
git-hooks.

---

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat and not feature/921 fixed setup.bat).
  If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labelled
  with internal
• You have not changed any dependency in pom.xml files or otherwise if runtime dependencies changed,
  you have updated our LICENSE.adoc
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

Checklist for tool commandlets

Have you added a new «tool» as commandlet? There are the following additional checks:

• The tool can be installed automatically (during setup via settings) or via the commandlet call
• The tool is isolated in its IDEasy project, see Sandbox Principle
• The new tool is added to the table of tools in LICENSE.asciidoc
• The new commandlet is a command-wrapper for «tool»
• Proper help texts for all supported languages are added here
• The new commandlet installs potential dependencies automatically
• The variables «TOOL»_VERSION and «TOOL»_EDITION are honored by your commandlet
• The new commandlet is tested on all platforms it is available for or tested on all platforms that are in scope of the linked issue

Checklist for GUI contributions

Did you make user-facing changes to the GUI? There are the following additional checks:

• You followed the ui-contribution-process.adoc and ui-structure.adoc
• The UI changes are designed in the Figma project and the design was approved in the team review
• You have added screenshots of the UI changes to the PR description

[coveralls]

Coverage Report for CI Build 40359343517

Coverage decreased (-0.01%) to 75.082%

Details

• Coverage decreased (-0.01%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 1 coverage regression across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/version/VersionSegment.java	1	89.76%

---

Coverage Stats

Relevant Lines:	19769
Covered Lines:	15497
Line Coverage:	78.39%
Relevant Branches:	8793
Covered Branches:	5948
Branch Coverage:	67.64%
Branches in Coverage %:	Yes
Coverage Strength:	3.37 hits per line

---

💛 - Coveralls