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 enhances the continuous integration process by introducing agnix validation. The primary goal is to maintain high standards for agent configurations and documentation by automatically checking for potential issues. This ensures that agent-related files adhere to defined guidelines, improving overall code quality and consistency across the repository.

Highlights

• Agnix Configuration: Added a .agnix.toml configuration file to the repository, including repository-specific false positive suppressions.
• CI Integration: Integrated an agnix validation job into the CI pipeline using a reusable ci-agnix.yml workflow.
• Validation Scope: Configured the CI job to validate agent configurations (CLAUDE.md, AGENTS.md, skills, hooks, MCP, plugins) on both push and pull request events.

Changelog

• .agnix.toml
  • Added the initial agnix configuration file, which specifies validation severity, file exclusions, the target code type, and a list of intentionally disabled rules with comments explaining their suppression.

Ignored Files

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

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 adds a configuration file for the agnix validation tool. The configuration is well-commented, but the global disabling of rules could be improved for better maintainability. I've added a specific comment with a suggestion to scope down the rule suppressions. On a related note, the AGENTS.md and CLAUDE.md files, which this configuration targets, appear to be identical. It might be worth consolidating them to reduce duplication.

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

[gemini-code-assist]

Disabling rules globally can be risky as it might suppress valid warnings in other files now or in the future. For better maintainability and to avoid unintended consequences, it's preferable to scope these exceptions as narrowly as possible.

If agnix supports it, consider using per-file configuration or inline comments to disable these rules only where necessary. For example:

• AGM-003 and AGM-004 could be disabled specifically for AGENTS.md.
• CC-MEM-009 could be disabled specifically for CLAUDE.md.

This would ensure that these rules are still enforced for other files where they might be relevant.