chore(labels): add type:security, AI review labels, and Tailwind color standard

[JacobPEvans]

Summary

• Add type:security label (991B1B/red-800) for security vulnerabilities and hardening
• Add claude-reviewed (FB923C/orange-400) and skip-ai-review (94A3B8/slate-400) AI review workflow labels
• Document Tailwind CSS palette requirement for all label colors in both labels.yml header and LABELS.md
• Add security issue template (security.yml) with vulnerability-specific fields
• Add full cross-repo sync procedure to LABELS.md for Phase 2 cleanup

Context

Audit of all JacobPEvans repos revealed label drift — wrong colors, missing labels, legacy defaults, and non-canonical labels across 6 of 7 repos. This PR updates the canonical source of truth. Phase 2 (cross-repo sync and legacy cleanup) is documented in LABELS.md and will be executed after this merges.

Test plan

• YAML validates (29 labels, no duplicates, all valid 6-char hex)
• All colors are Tailwind CSS palette values
• LABELS.md cross-checks against labels.yml
• Security issue template matches existing template patterns
• All pre-commit hooks pass (markdownlint, spelling, link check)

🤖 Generated with Claude Code

---

Important

Add new labels, a security issue template, enforce Tailwind CSS color standards, and document cross-repo sync procedure.

• Labels:
  • Add type:security label with color 991B1B.
  • Add AI review labels: claude-reviewed (color FB923C) and skip-ai-review (color 94A3B8).
• Templates:
  • Add security.yml issue template for security reports with specific fields.
• Documentation:
  • Update labels.yml and LABELS.md to require Tailwind CSS palette for label colors.
  • Document cross-repo sync procedure in LABELS.md.

^{This description was created by for c676324. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to c676324 in 7 seconds. Click for details.

• Reviewed 224 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 0 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

Workflow ID: wflow_QdaLD72K4Gs66QBs

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[gemini-code-assist]

Summary of Changes

Hello @JacobPEvans, 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 significantly enhances the repository's labeling system by standardizing label definitions and colors across all repositories. It addresses existing inconsistencies by introducing new labels for security and AI review processes, establishing a clear color standard based on Tailwind CSS, and providing a detailed guide for cross-repository label synchronization. The changes aim to improve issue tracking, streamline workflows, and ensure a consistent and maintainable labeling structure.

Highlights

• New Label Additions: Added a type:security label for security vulnerabilities and hardening, along with claude-reviewed and skip-ai-review labels to support AI review workflows.
• Color Standard Enforcement: Documented and enforced the use of Tailwind CSS palette hex values for all label colors in both labels.yml and LABELS.md to ensure visual consistency.
• Security Issue Template: Introduced a new security.yml issue template with specific fields for reporting security vulnerabilities, including severity, affected components, and priority.
• Cross-Repository Sync Procedure: Detailed a comprehensive procedure in LABELS.md for synchronizing labels across multiple repositories and cleaning up legacy GitHub default labels.

Changelog

• .github/ISSUE_TEMPLATE/security.yml
  • Added a new issue template for security reports, including fields for vulnerability description, affected components, severity assessment, additional context, priority, and estimated size.
• .github/labels.yml
  • Added a comment block to the header specifying Tailwind CSS palette as the required color standard for all labels.
  • Included the type:security label with a '991B1B' (red-800) color and description.
  • Added claude-reviewed and skip-ai-review labels with 'FB923C' (orange-400) and '94A3B8' (slate-400) colors respectively, for automated AI review workflows.
• docs/LABELS.md
  • Updated the 'Type Labels' table to include type:security with its corresponding semantic versioning impact.
  • Added a new 'AI Review Labels' section, documenting claude-reviewed and skip-ai-review and their usage in automated PR review workflows.
  • Introduced a 'Color Standards' section, outlining the requirement for Tailwind CSS palette hex values and providing guidelines for color assignment.
  • Added a 'Full Cross-Repo Sync Procedure' section, detailing steps and commands for syncing labels using gh label clone and migrating/deleting legacy GitHub default labels.
  • Updated the 'Issue Template Integration' table to include the new Security Report template and its associated type:security label.

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 introduces several improvements to repository management, including a new type:security label, AI review labels, and a new issue template for security reports. It also standardizes label colors on the Tailwind CSS palette and documents the label system and sync procedures extensively. The changes are well-structured and improve consistency. My review focuses on the new security issue template, where I've identified a configuration issue that will prevent priority and size labels from being automatically applied. The proposed suggestions will correct this, ensuring the template functions as intended.

[Copilot]

Pull request overview

This PR establishes canonical label standards by adding security and AI review labels, documenting Tailwind CSS color requirements, and providing comprehensive cross-repo synchronization procedures to address label drift across the JacobPEvans repository ecosystem.

Changes:

• Add type:security, claude-reviewed, and skip-ai-review labels with Tailwind CSS palette colors
• Document Tailwind CSS color standard requirement in both labels.yml header and LABELS.md
• Add security issue template with vulnerability-specific fields including severity assessment
• Add detailed cross-repo sync procedure with legacy label migration steps

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
.github/labels.yml	Adds three new labels (type:security, claude-reviewed, skip-ai-review) with Tailwind CSS palette colors and documents color standard requirement in header comments
docs/LABELS.md	Documents new labels, adds Color Standards section with Tailwind requirement, adds comprehensive cross-repo sync procedure, and updates issue template integration table
.github/ISSUE_TEMPLATE/security.yml	Adds new security issue template with vulnerability-specific fields (severity assessment, affected components) following established template patterns

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.