wehub-resource-sync
c889a57b6b
Test Suites / Build CI Environment (push) Has been cancelled
Test Suites / Basic Tests (push) Has been cancelled
Test Suites / End-to-End Tests (push) Has been cancelled
Test Suites / CLI Tests (push) Has been cancelled
Test Suites / Slow End-to-End Tests (push) Has been cancelled
Test Suites / Graph Database Tests (push) Has been cancelled
Test Suites / Vector DB Tests (push) Has been cancelled
Test Suites / Temporal Graph Test (push) Has been cancelled
Test Suites / Search Test on Different DBs (push) Has been cancelled
Test Suites / Example Tests (push) Has been cancelled
Test Suites / Notebook Tests (push) Has been cancelled
Test Suites / OS and Python Tests Ubuntu (push) Has been cancelled
Test Suites / OS and Python Tests Extended (push) Has been cancelled
Test Suites / LLM Test Suite (push) Has been cancelled
Test Suites / S3 File Storage Test (push) Has been cancelled
Test Suites / Run Integration Tests (push) Has been cancelled
Test Suites / MCP Tests (push) Has been cancelled
Test Suites / Docker Compose Test (push) Has been cancelled
Test Suites / Docker CI test (push) Has been cancelled
Test Suites / Relational DB Migration Tests (push) Has been cancelled
Test Suites / Distributed Cognee Test (push) Has been cancelled
Test Suites / DB Examples Tests (push) Has been cancelled
Test Suites / Test Completion Status (push) Has been cancelled
Test Suites / Claude Code Review (push) Has been cancelled
Test Suites / basic checks (push) Has been cancelled
build | Build and Push Cognee MCP Docker Image to dockerhub / docker-build-and-push (push) Has been cancelled
Scorecard supply-chain security / Scorecard analysis (push) Has been cancelled
build | Build and Push Docker Image to dockerhub / docker-build-and-push (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Core Functionality (3.11) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Core Functionality (3.12) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges with Different Graph Databases (kuzu, kuzu) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges with Different Graph Databases (neo4j, neo4j) (push) Has been cancelled
Weighted Edges Tests / Test Weighted Edges Examples (push) Has been cancelled
Weighted Edges Tests / Code Quality for Weighted Edges (push) Has been cancelled
80 lines
2.7 KiB
Markdown
Vendored
80 lines
2.7 KiB
Markdown
Vendored
Assistant Guidelines
|
||
These rules are absolutely imperative to adhere to. Comply with them precisely as they are outlined.
|
||
|
||
The agent must use sequential thinking MCP tool to work out problems.
|
||
|
||
Core Behavior Guidelines
|
||
|
||
Respond only to explicit requests. Do not add files, code, tests, or comments unless asked.
|
||
|
||
Follow instructions precisely. No assumptions or speculative additions.
|
||
|
||
Use provided context accurately.
|
||
|
||
Avoid extra output. No debugging logs or test harnesses unless requested.
|
||
|
||
Produce clean, optimized code when code is requested. Respect existing style.
|
||
|
||
Deliver complete, standalone solutions. No placeholders.
|
||
|
||
Limit file creation. Only create new files when necessary.
|
||
|
||
If you modify the model in a user's code, you must confirm with the user and never be sneaky. Always tell the user exactly what you are doing.
|
||
|
||
Communication & Delivery
|
||
|
||
9. Don't explain unless asked. Do not expose reasoning in outputs.
|
||
10. If unsure, say "I don't know." Avoid hallucinated content.
|
||
11. Maintain consistency across sessions. Refer to project memory and documentation.
|
||
12. Respect privacy and permissions. Never leak or infer secure data.
|
||
13. Prioritize targeted edits over full rewrites.
|
||
14. Optimize incrementally. Avoid unnecessary overhauls.
|
||
|
||
Spec.md Requirement
|
||
|
||
You must maintain a file named Spec.md. This file acts as the single source of truth for the project.
|
||
|
||
Rules:
|
||
|
||
Before starting any implementation, check if Spec.md already exists.
|
||
|
||
If it does not exist, create one using the template provided below.
|
||
|
||
Always update Spec.md before and after any major change.
|
||
|
||
Use the contents of Spec.md to guide logic, structure, and implementation decisions.
|
||
|
||
When updating a section, condense previous content to keep the document concise.
|
||
|
||
Spec.md Starter Template (Plain Text Format)
|
||
|
||
Title: Spec.md – Project Specification
|
||
|
||
Section: Purpose
|
||
Describe the main goal of this feature, tool, or system.
|
||
|
||
Section: Core Functionality
|
||
List the key features, expected behaviors, and common use cases.
|
||
|
||
Section: Architecture Overview
|
||
Summarize the technical setup, frameworks used, and main modules or services.
|
||
|
||
Section: Input and Output Contracts
|
||
List all inputs and outputs in a table-like format:
|
||
|
||
Input: describe the input data, its format, and where it comes from.
|
||
|
||
Output: describe the output data, its format, and its destination.
|
||
|
||
Section: Edge Cases and Constraints
|
||
List known limitations, special scenarios, and fallback behaviors.
|
||
|
||
Section: File and Module Map
|
||
List all important files or modules and describe what each one is responsible for.
|
||
|
||
Section: Open Questions or TODOs
|
||
Create a checklist of unresolved decisions, logic that needs clarification, or tasks that are still pending.
|
||
|
||
Section: Last Updated
|
||
Include the most recent update date and who made the update.
|