nimcode 0.4.5__tar.gz → 0.4.6__tar.gz

{nimcode-0.4.5 → nimcode-0.4.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.5
+Version: 0.4.6
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

nimcode-0.4.6/src/nimcode/__version__.py

@@ -0,0 +1 @@
+__version__ = "0.4.6"

{nimcode-0.4.5 → nimcode-0.4.6}/src/nimcode/repl.py

@@ -444,12 +444,14 @@ class NimcodeREPL:
                         "real requirements found during exploration. Do NOT invent a generic project.\n"
                         "3. Write the plan to a file inside '.nimcode/plans/'. CHOOSE a descriptive name derived from the task "
                         "or document AND append a timestamp to prevent naming collisions (e.g. 'imagease_pro_plan_20260730_1430.md').\n"
-                        "4. The plan must reference real files, real code, and real requirements found during exploration. "
-                        "Include specific files to create/modify (with full paths), actual code snippets or pseudocode for each "
-                        "change, dependencies to install, testing strategy, and step-by-step execution order.\n"
-                        "5. NEVER output a generic software-lifecycle template (Phase1: Research / Design / Development / "
-                        "Testing / Deployment) unless that is literally what the documents describe. NEVER use placeholders "
-                        "like [Insert Date].\n"
+                        "4. The plan MUST follow this strict technical structure:\n"
+                        "   - # [Descriptive Plan Title]\n"
+                        "   - ## Context: Brief summary of the current state based on actual files.\n"
+                        "   - ## Analysis / Root Cause: Detailed technical analysis of the problem or feature.\n"
+                        "   - ## Execution Plan (dosya-bazlı, sıralı): Step-by-step file modifications. MUST include specific files to create/modify (with full paths), and actual code snippets or pseudocode for each change. Format as: '### Task #1 - Update auth.py line 45'.\n"
+                        "   - ## Verification: Terminal commands to run to test the changes.\n"
+                        "5. NEVER output a generic software-lifecycle template (Phase1: MVP / Design / Development / "
+                        "Testing / Scale / Deployment). NEVER use placeholders like [Insert Date]. Focus strictly on code and files.\n"
                         "6. A good plan is one that another developer could follow to implement the feature without asking questions.\n"
                         "7. After writing the plan, you MUST overwrite the file '.nimcode/active_plan.txt' to contain exactly the path "
                         "of the plan you just created. This ensures the system tracks the current active plan."

{nimcode-0.4.5 → nimcode-0.4.6}/src/nimcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.5
+Version: 0.4.6
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

nimcode-0.4.5/src/nimcode/__version__.py

@@ -1 +0,0 @@
-__version__ = "0.4.5"