Commit `4547f55c9323`

Vincent Demeester <vincent@sbr.pm>

2026-04-15 16:15:19

feat: add 9 prompt templates for common workflows

Added gitcommit, jirabug, jira-release-note, pac-release, rewrite, spellen, spellfr, gitbranch, and markdown prompt templates adapted from chmouel/rc-config for Red Hat workflows, text polishing, and git operations. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Vincent Demeester <vincent@sbr.pm>

main

1 parent 2eba911

Changed files (9)

dots

agent

prompts

gitbranch.md

gitcommit.md

jira-release-note.md

jirabug.md

markdown.md

pac-release.md

rewrite.md

spellen.md

spellfr.md

@@ -0,0 +1,6 @@
+---
+description: Suggest a git branch name from a diff
+---
+Suggest a git branch name from this diff. Just output the branch name, nothing else. Do not add slashes or type prefixes like feature/bugfix etc. Separate words with hyphens.
+
+$@

@@ -0,0 +1,20 @@
+---
+description: Generate a commit message from staged changes
+---
+Generate a commit message from the staged changes (`git diff --cached`).
+
+Format:
+
+<type>: <subject>
+
+<body>
+
+Rules:
+- type: One of feat, fix, docs, style, refactor, perf, test, chore
+- Subject: 50 chars max, imperative mood, no ending period, capitalize first letter
+- Body: Cohesive paragraph or bullet points. Past tense. State what and why only (no how). Wrap at 72 chars.
+- Follow Conventional Commits 1.0.0
+- Skip obvious or minor changes in the body
+- Insert blank line between subject and body
+
+Output the commit message only — no extra text.

@@ -0,0 +1,8 @@
+---
+description: Create a concise Jira release note in Red Hat documentation style
+---
+Create a 3-line release note for a Jira ticket. The note should be concise and highlight the key changes or fixes. Use Red Hat documentation style. Do not use markdown formatting. Write as sentences, not bullet points (unless there are many distinct changes).
+
+If you need to go longer, that's fine.
+
+$@

@@ -0,0 +1,34 @@
+---
+description: Create a Red Hat Jira bug report from context
+---
+I am going to provide context about a bug. Create a Jira issue with a title using Jira formatting (not markdown) that I can paste directly into the Jira textbox.
+
+Use this template:
+
+h3. *Description of problem:*
+
+h3. *Workaround (if any):*
+
+h3. *Prerequisites (if any, like setup, operators/versions):*
+
+h3. *Steps to Reproduce*
+
+# <steps>
+
+h3. *Actual results:*
+
+h3. *Expected results:*
+
+h3. *Reproducibility (Always/Intermittent/Only Once):*
+
+h3. *Acceptance criteria:*
+
+*Definition of Done:*
+
+h3. *Build Details:*
+
+h3. *Additional info (Such as Logs, Screenshots, etc):*
+
+Here is the context:
+
+$@

@@ -0,0 +1,17 @@
+---
+description: Polish technical documentation in Red Hat/IBM style
+---
+You are a technical writer refining documentation for OpenShift. Your responsibilities:
+
+1. Correct spelling, grammar, punctuation, and formatting errors.
+2. Rephrase for clarity, conciseness, and fluency while maintaining technical accuracy.
+3. Ensure the tone aligns with professional documentation standards.
+4. Retain markdown formatting and enhance it for readability.
+5. Ensure conformance to Markdownlint rules:
+   - Single `#` for main heading, no skipping heading levels (keep metadata)
+   - Consistent list markers
+   - No trailing spaces
+   - Blank lines around headings and code blocks
+   - No bare URLs (use `[text](url)` format)
+
+$@

@@ -0,0 +1,10 @@
+---
+description: Generate PaC release notes from git log output
+---
+Here is the output of release changes. Make a list of all notable changes categorized by features/bugs/misc with emojis, output as markdown with a one-liner per change.
+
+Link each commit URL with prefix: https://github.com/openshift-pipelines/pipelines-as-code/commit/
+
+Add a Jira link like [SRVKP-XXX](https://issues.redhat.com/browse/SRVKP-XXX) for each change if there is one in the commit message.
+
+$@

@@ -0,0 +1,10 @@
+---
+description: Rewrite text to be better (auto-detects French or English)
+---
+First detect if the language used is English or French and act within that language. Try hard to detect the language.
+
+Rewrite the text to be better. Maintain the original meaning, context, and tone. Make sure to answer in the original language of the text.
+
+Only output the rewritten text, do not include any additional comments or explanations or any options.
+
+$@

@@ -0,0 +1,11 @@
+---
+description: Correct British English spelling in text
+---
+You are a model designed to correct only British English spelling in a text. Respond by returning exclusively the corrected text, without explanations, annotations, or other content.
+
+If you cannot correct the text, return it as is, unchanged.
+If the text is in Markdown, preserve the formatting at all costs.
+
+Here is the text to correct:
+
+$@

@@ -0,0 +1,11 @@
+---
+description: Corriger l'orthographe française dans un texte
+---
+Vous êtes un modèle conçu pour corriger uniquement les fautes de français dans un texte. Répondez en renvoyant exclusivement le texte corrigé, sans explications, annotations, ou autre contenu.
+
+Si vous ne pouvez pas corriger le texte, renvoyez-le tel quel, inchangé.
+Si le texte est en Markdown, conservez la mise en forme à tout prix.
+
+Voici le texte à corriger :
+
+$@

Commit 4547f55c9323

Commit `4547f55c9323`