Gen templates
Nyann (ငြမ်း) is Burmese for scaffolding. Nyann is a Claude Code plugin that sets up and maintains project governance.
npx -y skills add thettwe/nyann --skill gen-templatesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate GitHub PR and issue templates for this repository. TRIGGER ON: 'generate templates', 'add PR template', 'create issue templates', 'add GitHub templates', 'set up PR template', 'generate PR template', 'add pull request template', 'create bug report template', 'add feature request template'. Generates .github/PULL_REQUEST_TEMPLATE.md and .github/ISSUE_TEMPLATE/ with checklists matching the project's hook configuration.
SKILL.md
2.3 KB, as published. Nobody here has run it
gen-templates — Generate GitHub PR and Issue Templates
You are the gen-templates skill. You generate GitHub templates (PR template with quality checklists, bug report, feature request, and config) that mirror the project's quality gates.
When to trigger
- User asks to generate templates, add PR template, create issue templates
- User asks to set up PR template, add GitHub templates
- User asks to create bug report or feature request templates
DO NOT trigger on: general questions about GitHub templates, modifying templates not generated by nyann.
Execution flow
Phase 1: Resolve profile
- Resolve and load the active profile via
bin/load-profile.sh <name>(resolves preferences → CLAUDE.md markers →"default"fallback).
Phase 2: Preview
- Run
bin/gen-templates.sh --profile <profile> --target . --dry-runto preview. - Show the user:
- PR template checklist items (derived from hook phases)
- Commit scopes (from profile conventions)
- Issue templates that will be created
- Which files will be skipped (already exist)
Phase 3: Confirm and write
- Ask: "Write these templates to
.github/?" - On confirmation, run without
--dry-run. - If files already exist, mention
--forceto overwrite.
Phase 4: Suggest next steps
- Suggest:
- "Run
/nyann:gen-cito add a CI workflow" - "Commit and push to see templates on GitHub"
- "Run
Key constraints
- Existing template files are NOT overwritten unless
--forceis passed. This respects user customizations. - If the profile has no hooks, a minimal default checklist is generated.
- Issue templates use GitHub's YAML frontmatter for labels and assignees.
When to hand off
- "Add a CI workflow too" →
gen-ciskill. - "Apply branch protection" →
gh-protectskill. - "Commit these templates" →
commitskill.