Project Files

.pydev-tools

_ast

describe.py

do_work.py

docstrings.py

extract_function.py

extract.py

legacy_handler_2.py

legacy_handler_3.py

legacy_handler.py

migration.py

reference.py

rename.py

workspace_description.md

prompt_examples

dependency_version_migration.txt

hotfix_rework.txt

new_project.txt

performance_optimization.txt

refactory.txt

security_hardening.txt

source_tree_analysis.txt

test_coverage_expansion.txt

scripts

e2e_runPytest_test.cjs

setupVenv.mjs

smokeNew6Tools.ts

smokeNewTools.ts

verify_testfile_fix.ts

verifySetupVenv.ts

skills

pydev-mcp.md

src

tools

_profiling_worker_main.py

analyzeImportsAndDependencies.ts

buildPythonPackage.ts

checkForBugs.ts

checkForBugsInFile.ts

createProjectStructure.ts

createTestFileTool.ts

editTextFile.ts

editTextFileByLine.ts

findFiles.ts

generateRequirementsTxtTool.ts

getSetupStatusTool.ts

getWorkspaceRootTool.ts

inspectEnvironmentTool.ts

installModule.ts

listDirectory.ts

listTools.ts

profileProject.ts

pydevAuditDocstringsTool.ts

pydevDescribeWorkspaceTool.ts

pydevExtractFunctionTool.ts

pydevGenerateReferenceTool.ts

pydevMigrationAuditTool.ts

pydevSafeRenameTool.ts

readTextFile.ts

runLinterAndFormatter.ts

runLinterAndFormatterInFile.ts

runProjectCoverage.ts

runPython.ts

runPythonFile.ts

runPythonFileInteractive.ts

runPythonInteractive.ts

runRepl.ts

runTests.ts

runWithDebuggerTool.ts

saveTextFile.ts

scanProjectSecurity.ts

searchDirectory.ts

setupVenvTool.ts

switchPythonVersion.ts

typeCheckProjectTool.ts

uninstallModule.ts

config.ts

index.ts

test

run_tests.cjs

tools.test.cjs

manifest.json

package-lock.json

package.json

professor_headache.jpg

README.md

setup-venv.sh

tsconfig.json

prompt_examples / hotfix_rework.txt

Use the `pydev-mcp` MCP tools to rework the following function/logic in the existing codebase: [DESCRIBE FUNCTION AND ISSUE/REQUIREMENT].

Follow these steps in order:

1. **Baseline & Reproduction**:
   - Identify the target file and use `pydev_read_text_file` to read its content.
   - Create a reproduction test script in `tests/` that fails given the current implementation.
   - Run `pydev_run_tests` to confirm the failure.
2. **Diagnosis**:
   - Use `pydev_run_with_debugger` on the reproduction script to inspect local variables and the call stack to identify the root cause.
3. **Implementation & Rework**:
   - Apply the fix or rework using `pydev_edit_text_file` or `pydev_edit_text_file_by_line`.
   - After each edit, run `pydev_run_tests` to verify the fix.
   - Run `pydev_run_linter_and_formatter_in_file` to ensure the new code meets style standards.
4. **Quality Assurance**:
   - Run `pydev_type_check` on the affected module.
   - Run `pydev_scan_security` to ensure the fix doesn't introduce new vulnerabilities.
5. **Documentation**:
   - Update `doc/PROJECT-REPORT.md` to include a "Defect Resolution" section, quoting the debugger output (if relevant) and the final test results.

Do not skip any step. Confirm the result of each step before proceeding to the next one.