ci: add agnix validation to CI

[avifenesh]

Summary

• Add .agnix.toml configuration with repo-specific false positive suppressions
• Add agnix validation job to CI pipeline via reusable ci-agnix.yml workflow
• Validates agent configurations (CLAUDE.md, AGENTS.md, skills, hooks, MCP, plugins) on push and PR

Test plan

• CI passes with agnix validation step
• No false positive warnings in agnix output

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates agnix validation into the continuous integration pipeline. The primary goal is to automatically check agent configurations for correctness and prevent potential issues by suppressing known false positives, ensuring a more robust and reliable development process.

Highlights

• Agnix Configuration: Introduced a new .agnix.toml configuration file to define repository-specific false positive suppressions for agnix validation.
• CI Integration: Integrated an agnix validation job into the CI pipeline using a reusable ci-agnix.yml workflow.
• Agent Configuration Validation: Enabled validation of agent configurations (CLAUDE.md, AGENTS.md, skills, hooks, MCP, plugins) to run automatically on every push and pull request.

Changelog

• .agnix.toml
  • Added initial configuration for agnix validation.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci.yml

Activity

• No specific activity (comments, reviews, or progress updates) was provided in the context.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to add agnix validation to the CI pipeline by introducing an .agnix.toml configuration file. The configuration file itself is a good starting point. However, the pull request appears to be incomplete. The description mentions adding a ci-agnix.yml workflow file to enable the validation, but this file is missing from the changes. Additionally, the description states that repo-specific false positives will be suppressed, but the disabled_rules list in the configuration is empty, which could lead to CI failures. I have added a specific comment regarding this point.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The PR description states that this configuration includes 'repo-specific false positive suppressions', but the disabled_rules array is currently empty. If there are known rules that cause false positives for this repository, they should be added here to align with the PR's goal and prevent potential CI failures.