continue

To merge candidate rules and cases, the Skill reads candidate files, deduplicates them against the existing official library, and merges non-duplicate items to ensure a single, up-to-date governance source.

Deduplication works by reading collected candidate files from the candidates directory and checking them against existing items in the main repository, merging only non-duplicate entries to prevent redundant rules.

You need to run quarterly governance cycle merges after you have collected and human-reviewed candidate rules and cases, using the command with the specific quarter flag to synchronize updates.

Yes, the candidate merge process creates Git commits and tags. This ensures traceable updates and generates an update report after synchronizing the reviewed rules with the official repository.

The best way to reduce manual reconciliation is automating the merge of reviewed candidate rules into the official security library, ensuring deduplication and generating a traceable update report.

Yes, you must review candidate files before merging. The Skill synchronizes human-reviewed candidates with the main repository during quarterly governance cycles to maintain an official governance source.