External/5chan
1
0
Fork 0
mirror of https://github.com/bitsocialnet/5chan.git synced 2026-08-03 07:41:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(ai skills): correct stale branch names, rg flags, and commit scope rules

Browse Source 
Fixes deslop diffing against nonexistent main, an invalid rg --type tsx flag
in fix-merge-conflicts, a Codex-specific phrase leaking into the Claude/Cursor
inspect-elements description, and aligns commit-format with the required-scope
convention the commit skill and git history already use. Rewrites the readme
skill from 764 lines of Rails-specific guidance to a lean version matching
this Vite/Capacitor/Electron repo.
This commit is contained in:
Tommaso Casaburi
2026-07-03 13:58:34 +07:00
parent 57310867ec
commit 21bbc5f07c
24 changed files with 189 additions and 2262 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/commit-format/SKILL.md
+14 -7
View File
@@ -9,12 +9,12 @@ description: Formats GitHub commit messages following Conventional Commits style
Title only — raw markdown:
```
> **Commit title:** `type: short description here`
> **Commit title:** `type(scope): short description here`
```
Title with description — raw markdown:
```
> **Commit title:** `type: short description here`
> **Commit title:** `type(scope): short description here`
>
> Description sentence one. Description sentence two with `codeRef()` references.
```
@@ -25,31 +25,38 @@ Title with description — raw markdown:
2. Title goes after `**Commit title:**` wrapped in exactly ONE backtick pair
3. NEVER put backticks inside the title — the whole title is one code span, no nesting
4. Description uses backticks for code references — title does NOT
5. Conventional Commits types: `fix:`, `feat:`, `perf:`, `refactor:`, `docs:`, `chore:`
6. Use `perf:` for performance optimizations (not `fix:`)
5. Conventional Commits types: `fix`, `feat`, `perf`, `refactor`, `docs`, `chore`
6. Always include a scope — a short, human-readable area name (e.g. `reply modal`, `mod queue`), matching how this repo actually commits (see the `commit` skill)
7. Use `perf` for performance optimizations (not `fix`)
7. Description: 2-3 sentences about the solution, no bullet points, only if title isn't enough
## Wrong vs Right
❌ WRONG — missing backticks around title:
```
> **Commit title:** refactor: rename from /queue to /modqueue
> **Commit title:** refactor(mod queue): rename from /queue to /modqueue
```
❌ WRONG — backticks around individual words instead of whole title:
```
> **Commit title:** refactor: rename from `/queue` to `/modqueue`
> **Commit title:** refactor(mod queue): rename from `/queue` to `/modqueue`
```
✅ CORRECT — entire title in one backtick pair, no backticks inside:
❌ WRONG — missing scope:
```
> **Commit title:** `refactor: rename from /queue to /modqueue`
```
✅ CORRECT — entire title in one backtick pair, no backticks inside, scope present:
```
> **Commit title:** `refactor(mod queue): rename from /queue to /modqueue`
```
## Self-check
Before outputting, verify:
- [ ] Lines start with `>`
- [ ] Title is wrapped in exactly one backtick pair: `` `like this` ``
- [ ] Title has the form `type(scope): description`
- [ ] No backticks inside the title text
- [ ] Code references in description (not title) use backticks