@uocnv1998/agent-kit 1.0.2 → 1.0.4

package/bin/index.js

@@ -126,10 +126,8 @@ try {
             }
 
             console.log(`\n\n${colors.pipe} Initializing OpenSpec for the project...`);
-            // Only run init if openspec directory doesn't exist to avoid errors
-            if (!fs.existsSync(path.join(currentDir, 'openspec'))) {
-                execSync('openspec init --tools antigravity --force', { stdio: 'inherit', cwd: currentDir });
-            }
+            // Always run init to ensure tools are properly configured or refreshed
+            execSync('openspec init --tools antigravity --force', { stdio: 'inherit', cwd: currentDir });
 
             // Automatically configure OpenSpec to generate artifacts in Vietnamese
             const openspecConfigPath = path.join(currentDir, 'openspec', 'config.yaml');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uocnv1998/agent-kit",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "CLI tool to scaffold Agent Skills, Rules, and Workflows",
   "main": "bin/index.js",
   "bin": {

package/templates/.agent/dev/backend/rules/GEMINI.md

@@ -81,7 +81,7 @@ When applying the agent, inform the user:
 - **TDD (Test-Driven Development)**: Always write tests BEFORE writing the implementation. You must write both unit tests and feature tests. Run tests frequently and ensure the overall project test coverage rate is 80% or higher.
 - **Clean Code**: Run the appropriate code formatter based on the project's language and framework before finalizing changes. The specific formatting command may be defined in `AGENTS.md`.
 - **Security**: Use environment variables only in configuration files - never use `env()` directly outside of config files.
-- **OpenSpec & TDD Integration**: Whenever executing OpenSpec workflows (e.g., `/opsx:propose`, `/opsx:apply`), you MUST enforce TDD. During `/opsx:propose`, the `tasks.md` MUST explicitly break down features into `[ ] Write failing test (RED)`, `[ ] Implement (GREEN)`, and `[ ] Refactor`. During `/opsx:apply`, you are FORBIDDEN from writing implementation code before passing tests are demonstrated.
+- **OpenSpec & TDD Integration**: Whenever executing OpenSpec workflows (e.g., `/opsx:propose`, `/opsx:apply`), you MUST enforce TDD. You must write both unit tests and feature tests. During `/opsx:propose`, the `tasks.md` MUST explicitly break down features into `[ ] Write failing test (RED)`, `[ ] Implement (GREEN)`, and `[ ] Refactor`. During `/opsx:apply`, you are FORBIDDEN from writing implementation code before passing tests are demonstrated.
 
 ### 🌐 Documents (Workspace files)