Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

gen-templates

Étoiles6

Forks0

Mis à jour18 mai 2026 à 06:27

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

thettwe

thettwe/nyann

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

gen-templates

description

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-run to 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 --force to overwrite.

Phase 4: Suggest next steps

Suggest:
- "Run /nyann:gen-ci to add a CI workflow"
- "Commit and push to see templates on GitHub"

Key constraints

Existing template files are NOT overwritten unless --force is 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-ci skill.
"Apply branch protection" → gh-protect skill.
"Commit these templates" → commit skill.

Plus depuis ce dépôt

même dépôt

doctor

thettwe/nyann

Run a read-only hygiene + documentation audit on the current repo. TRIGGER when the user says "is this repo healthy", "check hygiene", "audit this repo" (when they mean inspect, not remediate), "what's drifted", "run doctor", "run a health check", "audit docs", "check for doc drift", "what's broken in this project", "are the hooks still installed", "/nyann:doctor". Do NOT trigger on "fix this repo" / "remediate" / "bring it into compliance" — those are retrofit (audit + fix). doctor reports, never writes. Do NOT trigger on "what does this repo do" (that's a docs pointer, not a hygiene audit).

2026-06-296

iac-apply

thettwe/nyann

Actually APPLY an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can mutate real cloud infrastructure. Re-runs the plan, shows it, confirms with the user, then invokes `bin/iac-apply.sh --apply` (adding `--confirm-destroy` only when the user explicitly confirms a destructive change). UNMISTAKABLY opt-in: apply is never the default, destructive applies need a second explicit confirmation. TRIGGER when the user says "terraform apply", "apply the infra change", "deploy this infrastructure", "tofu apply", "cdk deploy", "pulumi up", "helm upgrade", "kubectl apply", "apply the plan", "run the apply now", "yes apply it" (in an IaC context), "ship the infra change", "provision this", "/nyann:apply". DISAMBIGUATION — fire ONLY for IaC apply intent on a detected infra repo. Do NOT trigger on the generic word "apply": NOT "apply this code patch", NOT "apply the suggestion", NOT "apply formatting", NOT "apply a migration" (DB migrations are out of scope), NOT "apply for X". An infra signal is REQ

2026-06-296

iac-plan

thettwe/nyann

Preview an Infrastructure-as-Code change WITHOUT applying it. Runs `bin/iac-plan.sh`, which detects the repo's IaC tool (terraform, opentofu, aws-cdk, pulumi, helm, kubernetes, kustomize, ansible), shells out to the user's already-authenticated CLI, and renders a normalized add/change/destroy summary. READ-ONLY — it never mutates infrastructure. TRIGGER when the user says "terraform plan", "preview my infra change", "what will this deploy", "cdk diff", "pulumi preview", "show me the terraform diff", "dry-run the infra change", "what would terraform/tofu/cdk/pulumi do", "plan the infrastructure", "kubectl diff", "helm diff", "what does this deploy change", "/nyann:plan". DISAMBIGUATION — fire ONLY for IaC plan intent on a detected infra repo. Do NOT trigger on the bare word "plan": this is NOT project planning, NOT sprint/roadmap planning, NOT `sc:*` task planning, NOT Claude's ExitPlanMode / "make a plan" for code work. "plan a feature", "plan my week", "let's plan the refactor" → ignore. Require an infra sig

2026-06-296

thettwe/nyann

Open a GitHub pull request from the current branch, with a Conventional-Commits-style title and a body summarizing the commit range. TRIGGER when the user says "open a PR", "create a pull request", "push and PR", "submit this for review", "ship this PR", "open a draft PR", "file a PR for this branch", "/nyann:pr". Do NOT trigger on "merge the PR" / "approve the PR" / "review PR #N" — those are GitHub actions outside nyann's wedge. Do NOT trigger on "rebase" / "sync with main" / "update my branch" — that's the `sync` skill. Do NOT trigger when the user is on `main` or `master` (no PR to open); if detected, tell them to create a branch first and route to `new-branch`.

2026-06-296

settings

thettwe/nyann

Interactive settings menu for nyann preferences. View current values in a table, then pick one setting to change at a time via AskUserQuestion. Re-runnable anytime — does not require a full setup wizard. TRIGGER when the user says "change nyann settings", "nyann preferences", "configure nyann settings", "update my preferences", "toggle triage", "disable sentinel", "enable session triage", "/nyann:settings", "show nyann settings", "nyann config". ALSO trigger on direct shortcut: "/nyann:settings <key> <value>" — skip the menu and write the value directly. Do NOT trigger on "/nyann:setup" — that is the first-run wizard. Do NOT trigger on "/nyann:check-prereqs" — that inspects host tools, not nyann config.

2026-06-296

ship

thettwe/nyann

Open a PR and merge it in one step — combines `bin/pr.sh` create with `bin/wait-for-pr-checks.sh` polling and `gh pr merge`. Default mode enables GitHub's native auto-merge so the terminal returns immediately; `--client-side` polls in the foreground and merges when CI goes green. TRIGGER when the user says "ship this PR", "ship it", "open and merge", "PR and merge", "create PR and auto-merge it", "wait for CI then merge", "block until merged", "/nyann:ship". Do NOT trigger on "open a PR" alone (no merge intent) — that's the `pr` skill. Do NOT trigger on "merge this existing PR #N" — ship is PR-creation + merge, not standalone merge of an already-open PR. Do NOT trigger on "release X.Y.Z" — that's the `release` skill, which tags a merged commit rather than creating one.

2026-06-296

name

gen-templates

description

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-run to 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 --force to overwrite.

Phase 4: Suggest next steps

Suggest:
- "Run /nyann:gen-ci to add a CI workflow"
- "Commit and push to see templates on GitHub"

Key constraints

Existing template files are NOT overwritten unless --force is 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-ci skill.
"Apply branch protection" → gh-protect skill.
"Commit these templates" → commit skill.