@frenchtoastman/oh-my-groundcontrol 0.0.12 → 0.0.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@frenchtoastman/oh-my-groundcontrol",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.13",
|
|
4
4
|
"description": "An OpenCode plugin for multi-agent orchestration for structured planning with NASA-style guardrails.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: commit-protocol
|
|
3
|
+
description: Write concise commit messages with required type(scope) prefix based on current changes and user input.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Commit Protocol Skill
|
|
7
|
+
|
|
8
|
+
You enforce a strict, NASA-inspired "Traceability First" format for git commit messages.
|
|
9
|
+
|
|
10
|
+
## When to Use
|
|
11
|
+
|
|
12
|
+
**Always active.** You MUST use this exact format every time you create a git commit.
|
|
13
|
+
|
|
14
|
+
## Protocol Template
|
|
15
|
+
|
|
16
|
+
All commits must exactly match the following structure. Pay strict attention to the character limits.
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
type(Component): <Brief, imperative summary under 50 chars>
|
|
20
|
+
|
|
21
|
+
Description:
|
|
22
|
+
<Brief 1-2 sentence explanation of why this change is necessary and what it accomplishes. Wrapped at 72 chars.>
|
|
23
|
+
|
|
24
|
+
Changes:
|
|
25
|
+
- <Change 1>
|
|
26
|
+
- <Change 2>
|
|
27
|
+
|
|
28
|
+
Traceability:
|
|
29
|
+
- Traces to: [Issue # / REQ ID / None]
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
### 1. Type
|
|
33
|
+
Must be one of the following:
|
|
34
|
+
- `feat`: A new feature
|
|
35
|
+
- `fix`: A bug fix
|
|
36
|
+
- `docs`: Documentation only changes
|
|
37
|
+
- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
|
|
38
|
+
- `refactor`: A code change that neither fixes a bug nor adds a feature
|
|
39
|
+
- `test`: Adding missing tests or correcting existing tests
|
|
40
|
+
- `chore`: Changes to the build process or auxiliary tools and libraries such as documentation generation
|
|
41
|
+
|
|
42
|
+
### 2. Component
|
|
43
|
+
The module or component being modified.
|
|
44
|
+
- If modifying a specific component, use its name (e.g., `api`, `ui`, `auth`).
|
|
45
|
+
- If the commit spans multiple components or is repository-wide, use `(global)` or `(core)`.
|
|
46
|
+
|
|
47
|
+
### 3. Summary Line
|
|
48
|
+
- Must use imperative mood ("Add feature", not "Added feature").
|
|
49
|
+
- Must not end with a period.
|
|
50
|
+
- Must be strictly under 50 characters (including the `type(Component): ` prefix).
|
|
51
|
+
|
|
52
|
+
### 4. Description
|
|
53
|
+
- Explain *why* the change is necessary and *what* it accomplishes.
|
|
54
|
+
- Wrap text at 72 characters.
|
|
55
|
+
|
|
56
|
+
### 5. Changes
|
|
57
|
+
- A bulleted list of the specific technical changes made.
|
|
58
|
+
|
|
59
|
+
### 6. Traceability
|
|
60
|
+
- If resolving a specific issue or requirement, state it (e.g., `Issue #42` or `REQ-001`).
|
|
61
|
+
- If no specific tracking ID exists, state `None`.
|
|
62
|
+
|
|
63
|
+
## Examples
|
|
64
|
+
|
|
65
|
+
### Good Example
|
|
66
|
+
```
|
|
67
|
+
fix(auth): Prevent token leak on session timeout
|
|
68
|
+
|
|
69
|
+
Description:
|
|
70
|
+
The previous implementation kept the JWT in memory after the session
|
|
71
|
+
timeout event fired, leaving a brief window where it could be extracted.
|
|
72
|
+
|
|
73
|
+
Changes:
|
|
74
|
+
- Cleared token state immediately on timeout event trigger
|
|
75
|
+
- Added test coverage for session expiry cleanup
|
|
76
|
+
|
|
77
|
+
Traceability:
|
|
78
|
+
- Traces to: Issue #128
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
### Bad Example (Do Not Do This)
|
|
82
|
+
```
|
|
83
|
+
Fixed a bug in the auth system where tokens were leaking
|
|
84
|
+
|
|
85
|
+
I went in and found that the JWT was staying in memory after the session timed out. I fixed it by clearing the state earlier. Also added some tests.
|
|
86
|
+
```
|
|
87
|
+
*(Reason: Missing type, component, description block, bulleted changes, traceability, and summary exceeds 50 chars).*
|