agent-check

Agent-check maps audit targets to appropriate domain and config agents by analyzing file patterns and content. It determines which agents (eslint, typescript, prisma-database, etc.) should audit each file, producing a deterministic agents array for your audit workflow.

Yes. Agent-check applies file-pattern matching and content-pattern detection across repository targets and file paths in diverse project structures, handling configuration files, code files, and domain contexts in monorepos.

Agent-check produces a single, deterministic agents array listing required agents for auditing your targets. Feed this output directly to your audit planning step to ensure correct agent coverage before starting the audit.

Agent-check implements deduplication logic during pattern matching and agent mapping, ensuring each required agent appears only once in the final agents array regardless of how many targets reference it.

Agent-check recognizes file-pattern matching (file extensions, paths) and content-pattern detection (framework signatures, configuration markers) to identify appropriate agents. Specific patterns map to domain agents like eslint, typescript, and prisma-database.

No. Agent-check automatically maps targets to agents based on built-in pattern recognition. It requires audit targets and file paths as input; no agent pre-configuration is necessary.