@xingyu.wang/evoskills 2.1.0 → 2.2.0
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/.github/AI_CONSTITUTION.md +21 -1
- package/package.json +7 -1
- package/.github/EXECUTION_RULES.md +0 -105
|
@@ -88,6 +88,26 @@ When creating skill `_my-skill`, you only need to declare its tier and dependenc
|
|
|
88
88
|
|
|
89
89
|
---
|
|
90
90
|
|
|
91
|
+
## Mandatory Initialization Binding
|
|
92
|
+
|
|
93
|
+
The constitution defines **why** evolution and discipline are required.
|
|
94
|
+
The initialization protocol defines **how** every response is enforced.
|
|
95
|
+
|
|
96
|
+
### Authority and layering
|
|
97
|
+
|
|
98
|
+
1. **Constitution** (`.github/AI_CONSTITUTION.md`): immutable evolution principles
|
|
99
|
+
2. **Initialization protocol** (`.github/AI_INITIALIZATION.md`): mandatory 4-phase execution contract
|
|
100
|
+
3. **Instruction entrypoint** (`.github/copilot-instructions.md`): active loading and per-response gate
|
|
101
|
+
4. **Skill definitions** (`.agent/skills/*/SKILL.md`): implementation details
|
|
102
|
+
|
|
103
|
+
### Compliance contract
|
|
104
|
+
|
|
105
|
+
- A response is valid only when it satisfies all required initialization markers and checks.
|
|
106
|
+
- If any required phase is missing, execution must stop and resume from the missing phase.
|
|
107
|
+
- Evolution outputs (new rules/skills) must remain compatible with this enforcement chain.
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
91
111
|
## Glossary
|
|
92
112
|
|
|
93
113
|
| Term | Definition |
|
|
@@ -101,4 +121,4 @@ When creating skill `_my-skill`, you only need to declare its tier and dependenc
|
|
|
101
121
|
|
|
102
122
|
> **Version**: 2.1
|
|
103
123
|
> **Focus**: Evolution mechanism only (lean and focused)
|
|
104
|
-
> **Related Files**:
|
|
124
|
+
> **Related Files**: `.github/AI_INITIALIZATION.md`, `.github/copilot-instructions.md`, `AGENTS.md`
|
package/package.json
CHANGED
|
@@ -1,11 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@xingyu.wang/evoskills",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.2.0",
|
|
4
4
|
"description": "Evolution Skills CLI for installing and managing openskills-compatible AI skills.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"bin": {
|
|
7
7
|
"evoskills": "./evoskills"
|
|
8
8
|
},
|
|
9
|
+
"scripts": {
|
|
10
|
+
"version:patch": "npm version patch -m 'chore(release): bump version to %s'",
|
|
11
|
+
"version:minor": "npm version minor -m 'chore(release): bump version to %s'",
|
|
12
|
+
"version:major": "npm version major -m 'chore(release): bump version to %s'",
|
|
13
|
+
"postversion": "git push origin main --tags"
|
|
14
|
+
},
|
|
9
15
|
"files": [
|
|
10
16
|
"evoskills",
|
|
11
17
|
"README.md",
|
|
@@ -1,105 +0,0 @@
|
|
|
1
|
-
# Execution Rules
|
|
2
|
-
|
|
3
|
-
> Optional rules that enforce safe and predictable AI behavior. Install with evoskills; can be deleted if not needed for your use case.
|
|
4
|
-
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Overview
|
|
8
|
-
|
|
9
|
-
These 4 rules form the guardrails for reliable AI execution. They are **auto-enforced by the core system** when enabled, but can be selectively disabled or removed if your workflow doesn't require them.
|
|
10
|
-
|
|
11
|
-
**Install Status**: These rules are auto-installed by `evoskills init`. To disable, remove this file's entry from `.github/copilot-instructions.md`.
|
|
12
|
-
|
|
13
|
-
---
|
|
14
|
-
|
|
15
|
-
## Rule 1: Instruction Guard (_instruction-guard)
|
|
16
|
-
|
|
17
|
-
**Purpose**: Ensure project context is always loaded before responding.
|
|
18
|
-
|
|
19
|
-
**When Active**: Before each response, if project instruction file (`.github/copilot-instructions.md`) is not in current context, read it immediately.
|
|
20
|
-
|
|
21
|
-
**Why**: Prevents deviations due to missing project-specific requirements.
|
|
22
|
-
|
|
23
|
-
---
|
|
24
|
-
|
|
25
|
-
## Rule 2: Context Acknowledgment (_context-ack)
|
|
26
|
-
|
|
27
|
-
**Purpose**: Enable users to quickly verify the AI is following correct rules.
|
|
28
|
-
|
|
29
|
-
**When Active**: Each response must follow specified output format:
|
|
30
|
-
- Fixed prefix at start
|
|
31
|
-
- Polite address line
|
|
32
|
-
- Main content
|
|
33
|
-
- Reference list at end (showing which files/rules were consulted)
|
|
34
|
-
|
|
35
|
-
**Why**: Makes compliance transparent and auditable.
|
|
36
|
-
|
|
37
|
-
---
|
|
38
|
-
|
|
39
|
-
## Rule 3: File Output Guard (_file-output-guard)
|
|
40
|
-
|
|
41
|
-
**Purpose**: Prevent accidental file overwrites and unsafe operations.
|
|
42
|
-
|
|
43
|
-
**When Active**:
|
|
44
|
-
- **Forbidden**: Using HERE documents for file creation (`cat > file << 'EOF'`)
|
|
45
|
-
- **Required**: Use `create_file` or `replace_string_in_file` tools only
|
|
46
|
-
- **Large Files**: Files >5KB must be segmented to same file to avoid session limits
|
|
47
|
-
|
|
48
|
-
**Why**: Ensures file operations are safe, traceable, and controllable.
|
|
49
|
-
|
|
50
|
-
---
|
|
51
|
-
|
|
52
|
-
## Rule 4: Session Safety (_session-safety)
|
|
53
|
-
|
|
54
|
-
**Purpose**: Prevent session failure due to excessive output.
|
|
55
|
-
|
|
56
|
-
**When Active**: When estimated output length exceeds 5KB:
|
|
57
|
-
- Segment processing or write to file instead
|
|
58
|
-
- Don't output overly long content in single response
|
|
59
|
-
|
|
60
|
-
**Why**: Protects conversation session from breaking.
|
|
61
|
-
|
|
62
|
-
---
|
|
63
|
-
|
|
64
|
-
## How These Rules Work Together
|
|
65
|
-
|
|
66
|
-
```
|
|
67
|
-
Rule 1 (_instruction-guard)
|
|
68
|
-
↓ [load context]
|
|
69
|
-
Rule 2 (_context-ack)
|
|
70
|
-
↓ [format response]
|
|
71
|
-
Rule 3 (_file-output-guard)
|
|
72
|
-
↓ [file operations safe]
|
|
73
|
-
Rule 4 (_session-safety)
|
|
74
|
-
↓ [output within limits]
|
|
75
|
-
✅ Safe, predictable, auditable execution
|
|
76
|
-
```
|
|
77
|
-
|
|
78
|
-
---
|
|
79
|
-
|
|
80
|
-
## When to Disable
|
|
81
|
-
|
|
82
|
-
You can safely remove this file's reference from `.github/copilot-instructions.md` if:
|
|
83
|
-
|
|
84
|
-
1. You're using the AI in personal projects with low risk tolerance
|
|
85
|
-
2. Your workflow doesn't need output format enforcement
|
|
86
|
-
3. You want maximum flexibility without guardrails
|
|
87
|
-
|
|
88
|
-
However, we recommend keeping at least **Rule 1** (_instruction-guard) enabled for project-based work.
|
|
89
|
-
|
|
90
|
-
---
|
|
91
|
-
|
|
92
|
-
## Relationship to Evolution
|
|
93
|
-
|
|
94
|
-
These rules are **separate from evolution**. Evolution (in AI_CONSTITUTION.md) happens automatically when triggers fire. These rules ensure safe execution during evolution and regular tasks.
|
|
95
|
-
|
|
96
|
-
Think of it this way:
|
|
97
|
-
- **Constitution** = "How the AI learns"
|
|
98
|
-
- **Execution Rules** = "How the AI operates safely"
|
|
99
|
-
- **Skills** = "What the AI does"
|
|
100
|
-
|
|
101
|
-
---
|
|
102
|
-
|
|
103
|
-
> **Version**: 1.0
|
|
104
|
-
> **Install Source**: evoskills (auto-installed with `evoskills init`)
|
|
105
|
-
> **Customization**: Can be extended in project-specific instruction files
|