Skip to content

Commit 556097d

Browse files
MgldvdMgldvd
committed
🔧 chore(prompts): add shared commit and sync prompt templates
Add prompt/docs sets for Claude, Codex, GitHub, OpenCode, and VS Code command folders.\nInclude .sync.yml and OpenCode skill docs to standardize assistant workflows.
1 parent 9843e0f commit 556097d

17 files changed

Lines changed: 1025 additions & 0 deletions

File tree

‎.claude/commands/README.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Custom Commands
2+
3+
This folder contains custom prompt commands.
4+
5+
All command files here start with the `oo-` prefix on purpose.
6+
7+
## Why `oo-`?
8+
9+
- It makes these commands easy to find.
10+
- When you type `/oo-`, related commands are grouped together and listed quickly.
11+
- In the prompt window, they are easier to recognize as custom commands.
12+
13+
## Naming convention
14+
15+
- Use `oo-` at the start of every command file name.
16+
- Keep names short and descriptive.
17+
18+
Examples:
19+
20+
- `oo-sync.prompt.md`
21+
- `oo-commit.prompt.md`

.opencode/commands/commit.prompt.md renamed to .claude/commands/oo-commit.prompt.md

File renamed without changes.

‎.claude/commands/oo-sync.prompt.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
description: Sync files across workspace and branches using .sync.yml (2-step with explicit confirmation)
3+
agent: build
4+
---
5+
6+
GOAL
7+
Synchronize files in the workspace and across multiple branches.
8+
9+
GENERAL RULES (MANDATORY)
10+
- Read and apply ONLY what is defined in @.sync.yml.
11+
- Execution is strictly 2 steps:
12+
1) Produce a SIMPLE summary of what would be synchronized.
13+
2) Ask “Do you want to execute the synchronization? (reply exactly: yes / no)”. Do NOT execute anything unless the reply is exactly “yes”.
14+
- Do NOT delete files.
15+
- If @.sync.yml is missing or invalid, stop and report the error.
16+
- Use exactly `commit_message` from the YAML when committing.
17+
- If no changes exist in a branch, do not create a commit.
18+
- Process CURRENT branch first (if included in rule.branches), then the remaining branches in listed order.
19+
20+
CONTEXT
21+
!`git rev-parse --abbrev-ref HEAD`
22+
@.sync.yml
23+
24+
STEP 1 — SIMPLE SUMMARY OUTPUT
25+
26+
- Generate the summary in CONSOLE OUTPUT using shell printing.
27+
- If console output is not available, output the same content as a markdown code block.
28+
- The summary must mirror the structure of `.sync.yml`, minimal and without narrative text.
29+
30+
CONSOLE FORMAT:
31+
32+
commit_message: <value>
33+
34+
rules:
35+
- name: <rule.name>
36+
source: <source_of_truth.branch>:<source_of_truth.path>
37+
destinations:
38+
- <path>
39+
- <path>
40+
branches:
41+
- <branch>
42+
- <branch>
43+
changes:
44+
<branch>: create=<n> update=<n> unchanged=<n>
45+
<branch>: create=<n> update=<n> unchanged=<n>
46+
47+
Rules:
48+
- Only totals per branch (no file lists)
49+
- Keep output minimal
50+
- Preserve YAML order
51+
52+
After printing summary, ask exactly:
53+
54+
Do you want to execute the synchronization? (reply exactly: yes / no)
55+
56+
STOP.
57+
58+
STEP 2 — EXECUTION (ONLY IF “yes”)
59+
60+
1) Re-read @.sync.yml
61+
2) For each rule:
62+
- Process current branch first if included
63+
- Then process remaining branches in listed order
64+
3) For each branch:
65+
- Checkout branch
66+
- Copy from source_of_truth.branch + source_of_truth.path
67+
- Apply to each destinations[].path preserving structure
68+
- Do not modify anything else
69+
4) If changes exist:
70+
- Stage only destination paths
71+
- Commit using commit_message
72+
5) If no changes: skip commit
73+
74+
FINAL RESULT OUTPUT (console or markdown fallback)
75+
76+
result:
77+
<branch>: changed=yes|no rules=[rule1, rule2]

‎.codex/prompts/README.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Custom Commands
2+
3+
This folder contains custom prompt commands.
4+
5+
All command files here start with the `oo-` prefix on purpose.
6+
7+
## Why `oo-`?
8+
9+
- It makes these commands easy to find.
10+
- When you type `/oo-`, related commands are grouped together and listed quickly.
11+
- In the prompt window, they are easier to recognize as custom commands.
12+
13+
## Naming convention
14+
15+
- Use `oo-` at the start of every command file name.
16+
- Keep names short and descriptive.
17+
18+
Examples:
19+
20+
- `oo-sync.prompt.md`
21+
- `oo-commit.prompt.md`

‎.codex/prompts/oo-commit.prompt.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: commit
3+
description: Generate a Conventional Commit with emoji, create the commit and push it
4+
---
5+
6+
You are an assistant that generates Git commit messages following the **Conventional Commits** standard with a **favicon emoji** at the start, then creates the commit and pushes it to the current branch.
7+
8+
Instructions:
9+
10+
1. Analyze the staged changes to determine the correct commit type and scope.
11+
12+
2. Generate a commit message using this format:
13+
14+
<emoji> <type>(<scope>): <short title>
15+
16+
<longer description if needed>
17+
18+
3. Follow these emoji mappings:
19+
✨ feat — new feature
20+
🐛 fix — bug fix
21+
📝 docs — documentation change
22+
🎨 style — formatting or style change (no logic)
23+
♻️ refactor — code refactor (no behavior change)
24+
⚡ perf — performance improvement
25+
✅ test — tests added or updated
26+
🔧 chore — maintenance, build, or CI changes
27+
🚑 hotfix — urgent production fix
28+
29+
4. Always include a scope describing the affected area.
30+
31+
5. Keep the short title under 72 characters.
32+
33+
6. After generating the message, run:
34+
35+
git commit -m "<generated message>" && git push
36+
37+
Goal: Create and push a clean, emoji-enhanced Conventional Commit message automatically.

‎.codex/prompts/oo-sync.prompt.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
description: Sync files across workspace and branches using .sync.yml (2-step with explicit confirmation)
3+
agent: build
4+
---
5+
6+
GOAL
7+
Synchronize files in the workspace and across multiple branches.
8+
9+
GENERAL RULES (MANDATORY)
10+
- Read and apply ONLY what is defined in @.sync.yml.
11+
- Execution is strictly 2 steps:
12+
1) Produce a SIMPLE summary of what would be synchronized.
13+
2) Ask “Do you want to execute the synchronization? (reply exactly: yes / no)”. Do NOT execute anything unless the reply is exactly “yes”.
14+
- Do NOT delete files.
15+
- If @.sync.yml is missing or invalid, stop and report the error.
16+
- Use exactly `commit_message` from the YAML when committing.
17+
- If no changes exist in a branch, do not create a commit.
18+
- Process CURRENT branch first (if included in rule.branches), then the remaining branches in listed order.
19+
20+
CONTEXT
21+
!`git rev-parse --abbrev-ref HEAD`
22+
@.sync.yml
23+
24+
STEP 1 — SIMPLE SUMMARY OUTPUT
25+
26+
- Generate the summary in CONSOLE OUTPUT using shell printing.
27+
- If console output is not available, output the same content as a markdown code block.
28+
- The summary must mirror the structure of `.sync.yml`, minimal and without narrative text.
29+
30+
CONSOLE FORMAT:
31+
32+
commit_message: <value>
33+
34+
rules:
35+
- name: <rule.name>
36+
source: <source_of_truth.branch>:<source_of_truth.path>
37+
destinations:
38+
- <path>
39+
- <path>
40+
branches:
41+
- <branch>
42+
- <branch>
43+
changes:
44+
<branch>: create=<n> update=<n> unchanged=<n>
45+
<branch>: create=<n> update=<n> unchanged=<n>
46+
47+
Rules:
48+
- Only totals per branch (no file lists)
49+
- Keep output minimal
50+
- Preserve YAML order
51+
52+
After printing summary, ask exactly:
53+
54+
Do you want to execute the synchronization? (reply exactly: yes / no)
55+
56+
STOP.
57+
58+
STEP 2 — EXECUTION (ONLY IF “yes”)
59+
60+
1) Re-read @.sync.yml
61+
2) For each rule:
62+
- Process current branch first if included
63+
- Then process remaining branches in listed order
64+
3) For each branch:
65+
- Checkout branch
66+
- Copy from source_of_truth.branch + source_of_truth.path
67+
- Apply to each destinations[].path preserving structure
68+
- Do not modify anything else
69+
4) If changes exist:
70+
- Stage only destination paths
71+
- Commit using commit_message
72+
5) If no changes: skip commit
73+
74+
FINAL RESULT OUTPUT (console or markdown fallback)
75+
76+
result:
77+
<branch>: changed=yes|no rules=[rule1, rule2]

‎.github/prompts/oo-commit.prompt.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: commit
3+
description: Generate a Conventional Commit with emoji, create the commit and push it
4+
---
5+
6+
You are an assistant that generates Git commit messages following the **Conventional Commits** standard with a **favicon emoji** at the start, then creates the commit and pushes it to the current branch.
7+
8+
Instructions:
9+
10+
1. Analyze the staged changes to determine the correct commit type and scope.
11+
12+
2. Generate a commit message using this format:
13+
14+
<emoji> <type>(<scope>): <short title>
15+
16+
<longer description if needed>
17+
18+
3. Follow these emoji mappings:
19+
✨ feat — new feature
20+
🐛 fix — bug fix
21+
📝 docs — documentation change
22+
🎨 style — formatting or style change (no logic)
23+
♻️ refactor — code refactor (no behavior change)
24+
⚡ perf — performance improvement
25+
✅ test — tests added or updated
26+
🔧 chore — maintenance, build, or CI changes
27+
🚑 hotfix — urgent production fix
28+
29+
4. Always include a scope describing the affected area.
30+
31+
5. Keep the short title under 72 characters.
32+
33+
6. After generating the message, run:
34+
35+
git commit -m "<generated message>" && git push
36+
37+
Goal: Create and push a clean, emoji-enhanced Conventional Commit message automatically.

‎.github/prompts/oo-sync.prompt.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
description: Sync files across workspace and branches using .sync.yml (2-step with explicit confirmation)
3+
agent: build
4+
---
5+
6+
GOAL
7+
Synchronize files in the workspace and across multiple branches.
8+
9+
GENERAL RULES (MANDATORY)
10+
- Read and apply ONLY what is defined in @.sync.yml.
11+
- Execution is strictly 2 steps:
12+
1) Produce a SIMPLE summary of what would be synchronized.
13+
2) Ask “Do you want to execute the synchronization? (reply exactly: yes / no)”. Do NOT execute anything unless the reply is exactly “yes”.
14+
- Do NOT delete files.
15+
- If @.sync.yml is missing or invalid, stop and report the error.
16+
- Use exactly `commit_message` from the YAML when committing.
17+
- If no changes exist in a branch, do not create a commit.
18+
- Process CURRENT branch first (if included in rule.branches), then the remaining branches in listed order.
19+
20+
CONTEXT
21+
!`git rev-parse --abbrev-ref HEAD`
22+
@.sync.yml
23+
24+
STEP 1 — SIMPLE SUMMARY OUTPUT
25+
26+
- Generate the summary in CONSOLE OUTPUT using shell printing.
27+
- If console output is not available, output the same content as a markdown code block.
28+
- The summary must mirror the structure of `.sync.yml`, minimal and without narrative text.
29+
30+
CONSOLE FORMAT:
31+
32+
commit_message: <value>
33+
34+
rules:
35+
- name: <rule.name>
36+
source: <source_of_truth.branch>:<source_of_truth.path>
37+
destinations:
38+
- <path>
39+
- <path>
40+
branches:
41+
- <branch>
42+
- <branch>
43+
changes:
44+
<branch>: create=<n> update=<n> unchanged=<n>
45+
<branch>: create=<n> update=<n> unchanged=<n>
46+
47+
Rules:
48+
- Only totals per branch (no file lists)
49+
- Keep output minimal
50+
- Preserve YAML order
51+
52+
After printing summary, ask exactly:
53+
54+
Do you want to execute the synchronization? (reply exactly: yes / no)
55+
56+
STOP.
57+
58+
STEP 2 — EXECUTION (ONLY IF “yes”)
59+
60+
1) Re-read @.sync.yml
61+
2) For each rule:
62+
- Process current branch first if included
63+
- Then process remaining branches in listed order
64+
3) For each branch:
65+
- Checkout branch
66+
- Copy from source_of_truth.branch + source_of_truth.path
67+
- Apply to each destinations[].path preserving structure
68+
- Do not modify anything else
69+
4) If changes exist:
70+
- Stage only destination paths
71+
- Commit using commit_message
72+
5) If no changes: skip commit
73+
74+
FINAL RESULT OUTPUT (console or markdown fallback)
75+
76+
result:
77+
<branch>: changed=yes|no rules=[rule1, rule2]

‎.opencode/commands/README.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Custom Commands
2+
3+
This folder contains custom prompt commands.
4+
5+
All command files here start with the `oo-` prefix on purpose.
6+
7+
## Why `oo-`?
8+
9+
- It makes these commands easy to find.
10+
- When you type `/oo-`, related commands are grouped together and listed quickly.
11+
- In the prompt window, they are easier to recognize as custom commands.
12+
13+
## Naming convention
14+
15+
- Use `oo-` at the start of every command file name.
16+
- Keep names short and descriptive.
17+
18+
Examples:
19+
20+
- `oo-sync.prompt.md`
21+
- `oo-commit.prompt.md`

0 commit comments

Comments
 (0)