mirror of
https://github.com/bitsocialnet/5chan.git
synced 2026-08-03 07:41:04 +02:00
Tommaso CasaburiandClaude Opus 4.6
189d1c2165
Mirrors .cursor and .codex structure with Claude model assignments: - haiku for lighter tasks (translator, browser-check, profiler) - sonnet for standard tasks (code-quality, plan-implementer, etc.) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| issue-format | Formats GitHub issue titles and descriptions for tracking problems that were fixed. Use when proposing or implementing code changes, creating GitHub issues, or when the user asks for issue suggestions. |
Issue Format
Template (copy this structure exactly)
Raw markdown:
> **GitHub issue:**
> - **Title:** `Short issue title here`
> - **Description:** Description sentence one. Sentence two with `codeRef()` references.
Rules
- Use markdown blockquote (
>prefix) — no exceptions - Title goes after
**Title:**wrapped in exactly ONE backtick pair - NEVER put backticks inside the title — the whole title is one code span, no nesting
- Description uses backticks for code references — title does NOT
- Title: as short as possible
- Description: 2-3 sentences about the problem (not the solution), present tense
Wrong vs Right
❌ WRONG — missing backticks around title:
> - **Title:** Mod queue should use /modqueue instead of /queue
❌ WRONG — backticks around individual words instead of whole title:
> - **Title:** Mod queue should use `/modqueue` instead of `/queue`
✅ CORRECT — entire title in one backtick pair, no backticks inside:
> - **Title:** `Mod queue should use /modqueue instead of /queue`
Self-check
Before outputting, verify:
- Lines start with
> - Title is wrapped in exactly one backtick pair:
`like this` - No backticks inside the title text
- Code references in description (not title) use backticks