Files
cmba-bylaws/.ai/skills/cmba-historical-bylaws/SKILL.md

2.0 KiB

name: cmba-historical-bylaws description: Use when answering questions about historical CMBA constitution/bylaws text from this repository's git history. This skill restricts references to the approved historical sources only: the initial commit containing the 2016 constitution/bylaws content, plus the tagged releases 2022-01-09, 2023, and 2024. Do not use newer draft, rc, test, or other tags as authority.

CMBA Historical Bylaws

Use this skill when the user asks what the CMBA rules/bylaws said in a prior year, how language changed over time, or to quote or compare historical versions.

Approved sources

Read references/source-map.md first. Treat its whitelist as authoritative.

Only use these git refs as historical authority:

  • 1e16926c5f76989d8821dc3f2b0df0c1c500e8e9 for the imported 2016 constitution/bylaws text
  • refs/tags/2022-01-09
  • refs/tags/2023
  • refs/tags/2024

Do not cite or summarize newer tags such as draft*, rc*, v2026*, or similar release-prep tags.

Workflow

  1. Identify which approved version or comparison the user wants.
  2. Use the path listed in references/source-map.md for that ref.
  3. Prefer direct git reads over working tree files, for example:
    • git show refs/tags/2024:src/cmba-bylaws.md
    • git show 1e16926c5f76989d8821dc3f2b0df0c1c500e8e9:content
  4. When comparing versions, use git diff --word-diff=color <old-ref> <new-ref> -- <path> and adjust paths if the file moved between refs.
  5. In the answer, name the exact ref and the document path used.

Guardrails

  • Be explicit about dates and refs. The initial commit date is 2021-11-09, but it imports the 2016 constitution/bylaws text.
  • If a user asks for "latest" historical bylaws, interpret that as the latest approved historical tag: refs/tags/2024.
  • If a request would rely on an unapproved newer tag, say that newer tags are drafts and are intentionally excluded from historical reference.
  • If wording differs because of formatting or conversion, say so rather than claiming a substantive rule change.