GitHub Templates

render_template(name, fields) = convention, not a runtime function: look up the named template's reference file, fill fields per its spec, use the resulting markdown. Lookup-and-fill happens inside the agent.

Workflow

1. Resolve name against Template Index. Unknown → stop: "Unknown template <name>. Known templates: <list>." No fuzzy-matching.
2. Read reference file (path in index) — authoritative for structure + field spec.
3. Validate fields per Field Conventions. Missing required → stop and list them. Extra fields → drop silently.
4. Fill fields per the reference → return the markdown string; never write to disk.

Field Conventions

Rules:

• Required field with no value → stop with a clear error listing the missing field(s).
• Optional field (?) with no value → omit the section entirely; no empty headings or placeholders.
• List with zero items → treat as absent (omit the section).
• Field values inserted verbatim — the caller handles markdown escaping within values.

Template Index

Removed Templates

Template removed → add a row here with the replacement so old names get a clear migration path.

Reference File Format

Every file under references/ follows this shape:

# <Template name>

## Purpose

One-line description of when this template is used.

## Fields

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| summary | string | yes | One-line summary of the change |
| changes | list<string> | yes | Per-file change descriptions |
| closes | issue_ref | yes | Issue number this PR closes |
| test_command | string? | no | Test command if applicable |

## Template

\`\`\`markdown
## Summary

{summary}

## Changes

{changes}

## How to verify

{test_command?}
{manual_verification?}

Closes {closes}
\`\`\`

Field markers in the template body:

• {field} — required; render verbatim.
• {field?} — optional; absent → line omitted entirely (including surrounding whitespace).
• {field} for a list field — rendered as a bullet list.

Constraints

• Never read template reference files outside references/.
• Never invent fields not in the reference spec.
• Never emit empty sections, placeholder text, or {field} markers in the output.
• Never write to disk — return the string; the caller decides what to do with it.
• Never fuzzy-match template names — exact match against the index or error.
• Reference files are the single source of truth; if this skill's body conflicts with a reference file, the reference file wins.