Skip to content

[Audit] Canonical Config Files (labels, issue-types, issue-fields) #903

Open

Description

@ashleyshaw

Overview

Comprehensive audit of canonical configuration files that define labels, issue types, issue fields, and automation relationships.

In-Scope

  • Validate consistency across .github/labels.yml, .github/issue-types.yml, .github/issue-fields.yml, and .github/labeler.yml
  • Audit colour strategy and label family coherence
  • Confirm issue type and template alignment
  • Confirm issue fields and automation compatibility

Out-of-Scope

  • Non-canonical label sets outside repository governance files
  • UI-only edits that do not affect canonical mappings

Current Problems

  1. Label strategy consistency is unclear at scale.
  2. Type-template-label mapping has potential drift.
  3. Issue fields usage and automation compatibility are not fully documented.
  4. Config interdependencies are not represented as a single source of truth.

Acceptance Criteria

  • Label colours and families validated against strategy
  • Issue types aligned to templates and labels
  • Issue fields validated for expected usage
  • Config interdependencies documented
  • Deprecations/removals identified

Deliverables

  • Config validation report
  • Mapping tables (type-template-label-field)
  • Dependency diagram and guide
  • Prioritised remediation plan

Related Files

  • .github/labels.yml
  • .github/labeler.yml
  • .github/issue-types.yml
  • .github/issue-fields.yml
  • docs/LABEL_STRATEGY.md
  • docs/LABELING.md
  • docs/ISSUE_TYPES.md
  • docs/ISSUE_FIELDS.md
  • docs/CANONICAL_CONFIGS_GUIDE.md

Agent skill governance audit

Audit every currently available personal and LightSpeed team skill for direct references to, or implicit rules about, issue types, labels, titles, fields, branch types, branch labels and labeler behaviour. Check the current develop branch of lightspeedwp/.github; canonical configuration takes precedence over documentation. Distinguish confirmed conflicts from possible dependencies, order affected skills by risk, and produce one individually copy-ready review prompt per affected skill. This is a read-only audit: propose complete revisions and obtain separate approval before changing any skill or record.

Canonical files: .github/issue-types.yml, .github/issue-fields.yml, .github/branch-labels.yml, .github/branch-types.yml, .github/labels.yml, .github/labeler.yml.

Supporting docs: AUTOMATION.md, AUTOMATION_GOVERNANCE.md, BRANCHING_STRATEGY.md, BRANCH_TYPE_PRIORITY_MAPPING.md, BRANCH_CONTEXT_MAPPING.md, ISSUE_LABELS.md, ISSUE_TYPES.md, ISSUE_TRIAGE_LABELING.md, ISSUE_TRIAGE_AUTOMATION.md, ISSUE_CREATION_GUIDE.md, ISSUE-TRIAGE-GUIDE.md, ISSUE_TRIAGE.md, LABELING.md, PR_TEMPLATE_VALIDATION.md, PR_LABELS.md, PR_GOVERNANCE.md, LABEL_STRATEGY.md, LABEL_COLOR_STRATEGY.md, LABELING_GOVERNANCE.md, ISSUE_PR_TITLE_GOVERNANCE.md, ISSUE_FIELDS.md.


Definition of Ready (DoR)

  • Clear problem statement and expected outcome
  • Acceptance criteria defined
  • Related issues/dependencies identified
  • Required resources/approvals listed

Definition of Done (DoD)

  • All acceptance criteria met
  • Changes tested and validated
  • Documentation updated
  • Changes merged and deployed
  • Stakeholders notified

Activity

  1. linear-code commented on Jun 8, 2026

    @linear-code
  2. github-actions commented on Jun 8, 2026

    @github-actions
    Contributor

    ⚠️ This issue does not follow a required issue template.

    Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)

    The issue will remain open and flagged until the body is corrected.
    Please update the issue with one of the official templates:

    If this was opened by automation, update the automation to preserve the template sections before creating the issue.

  3. added this to the v1.1 milestone on Jul 22, 2026
  4. self-assigned this
    on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

Medium

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions