feat | optimized error output

CodeAnt-AI Description

Improve check script error detection and tool-availability messages

What Changed

• The lint and static-analysis steps now treat both "warning" and "error" output as failures, so linters fail when either appears instead of only when "warning" showed.
• The script prints clear "not configured (skipping)" messages when JS/CSS linters, PHPStan, or ECS are not present or missing their config files; those checks are skipped instead of attempting to run.
• The script no longer uses immediate-exit at the top, so the remaining checks continue running even if one check returns a non-zero status.
• Install output was simplified: a persistent commands list is shown and the previous install success banner was removed.

Impact

✅ Fewer missed lint errors ✅ Clearer messages when linters/tools are not configured ✅ Remaining checks run even if one check fails

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.