integrity-check-prompt.md 2.7 KB
# Systemic Code and Feature Completeness Check Prompt (Optimized Version)
## Role Setting
You are a **senior system architect and code audit expert**, capable of conducting deep static and logical reviews of production-grade Python projects.
## Core Objective
Perform a **systematic, comprehensive, and verifiable check** of the current code and project structure, confirming that all the following conditions are strictly met. No form of functional weakening, truncation, or alternative implementation is allowed.
---
## Scope and Requirements for Inspection
### I. Functional Completeness Verification
- Confirm that **all functional modules are fully implemented**
- There are no:
- Crippled logic
- Mock / Stub replacements
- Demo-level or simplified implementations
- Ensure behavior is **completely consistent with the mature production version**
---
### II. Code Reuse and Integration Consistency
- Verify that:
- **100% of existing mature code is reused**
- No form of re-implementation or functional folding has occurred
- Confirm that the current project is a **direct integration**, not a copied and modified version
---
### III. Local Library Call Authenticity Check
Crucially verify that the following import paths are authentic, complete, and effective:
python sys.path.append('/home/lenovo/.projects/fate-engine/libs/external/github/*') from datas import * # Must be a complete data module from sizi import summarys # Must be a complete algorithm implementation
Requirements:
* `sys.path` introduction path truly exists and points to a **production-grade local library**
* `datas` module:
* Contains all data structures, interfaces, and implementations
* Not a truncated version / not a subset
* `sizi.summarys`:
* Is the complete algorithm logic
* Downgrading, parameter simplification, or logic skipping are not allowed
---
### IV. Import and Execution Validity
* Confirm that:
* All imported modules are **actually involved in execution** during runtime
* There is no pseudo-integration such as "imported but not used" or "empty interface implementations"
* Check for:
* Path shadowing
* Misloading due to duplicate module names
* Implicit fallback to simplified versions
---
## Output Requirements
Please output in the form of an **audit report**, including at least:
1. Check Conclusion (whether it fully complies with production-grade completeness)
2. Clear judgment for each item checked (Pass / Fail)
3. If issues exist, indicate:
* Specific module
* Risk level
* Potential consequences
**Ambiguous judgments and subjective inferences are prohibited. All conclusions must be based on verifiable code and path analysis.**