docs: Replace issue templates with focused, practical issues

- Removed 25 verbose templates
- Added 20 focused, actionable issues
- Categories: bugs, security, cleanup, docs, enhancements
- Each issue has clear problem, fix, and testing instructions

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

Author: hackdartstorm

.github/ISSUES_TO_CREATE/001_bug_prime_checker.md

@@ -1,52 +1,41 @@
 ---
-title: "BUG: Prime number checker has inverted logic in basics/03_control_flow/02_check_prime.py"
-labels: ["bug", "good first issue"]
-assignees: []
+title: "BUG: Prime number checker returns incorrect results"
+labels: ["bug", "good first issue", "priority: high"]
 ---
 
 ## Bug Description
 
-The prime number checking logic in `basics/03_control_flow/02_check_prime.py` is inverted, causing incorrect results.
+The prime number checker in `basics/03_control_flow/02_check_prime.py` has inverted logic that returns wrong results.
 
 ## Problem
 
-The final if-else block has the logic reversed:
-
+In the final if-else block (lines 13-16):
 ```python
 if(prime):
-    prime = False  # This should be True
+    prime = False  # Wrong! Should be True
 else:
-    prime = True   # This should be False
+    prime = True   # Wrong! Should be False
 ```
 
 ## Expected Behavior
 
-- Prime numbers (2, 3, 5, 7, 11, etc.) should return `True`
-- Non-prime numbers should return `False`
-
-## Current Behavior
+| Input | Expected | Actual |
+|-------|----------|--------|
+| 7     | True     | False  |
+| 10    | False    | True   |
+| 2     | True     | False  |
 
-- Prime numbers return `False`
-- Non-prime numbers return `True`
+## Fix
 
-## Files Affected
+Remove lines 13-16 entirely. The logic before this block already sets `prime` correctly.
 
+## Files
 - `basics/03_control_flow/02_check_prime.py`
 
-## Suggested Fix
-
-Swap the assignments in the final if-else block:
-
-```python
-if(prime):
-    prime = True
-else:
-    prime = False
+## Testing
+```bash
+cd basics/03_control_flow
+python 02_check_prime.py
+# Enter 7 → should show True
+# Enter 10 → should show False
 ```
-
-Or simply remove the final if-else block entirely since the logic is already correct before it.
-
-## How to Test
-
-1. Run the script with input `7` (prime number) - should output `True`
-2. Run the script with input `10` (non-prime) - should output `False`

.github/ISSUES_TO_CREATE/002_bug_sum_division.md

@@ -0,0 +1,41 @@
+---
+title: "BUG: Function named 'sum()' performs division instead of addition"
+labels: ["bug", "good first issue"]
+---
+
+## Bug Description
+
+The function `sum()` in `basics/09_error_handling/01_try_except.py` performs division instead of addition, which is confusing and incorrect.
+
+## Problem
+
+```python
+def sum(a: int, b: int) -> int:
+    result = a / b  # This is division, not addition!
+    return result
+```
+
+Issues:
+1. Function named `sum` but divides
+2. Type hint says `-> int` but division returns `float`
+3. Misleading for learners
+
+## Fix
+
+Rename function to `divide()` and fix the type hint:
+
+```python
+def divide(a: int, b: int) -> float:
+    result = a / b
+    return result
+```
+
+## Files
+- `basics/09_error_handling/01_try_except.py`
+
+## Testing
+```bash
+cd basics/09_error_handling
+python 01_try_except.py
+# Enter 10 and 2 → should show 5.0 (division makes sense here)
+```

.github/ISSUES_TO_CREATE/003_bug_hello_world.md

@@ -0,0 +1,40 @@
+---
+title: "BUG: Debug output in first hello world example"
+labels: ["bug", "good first issue"]
+---
+
+## Bug Description
+
+The very first file beginners run (`basics/01_introduction/01_hello_world.py`) has debug output that should be removed.
+
+## Problem
+
+```python
+print("ram")         # Debug output - should be removed
+print("Hello World")
+```
+
+## Expected
+
+Only print "Hello World"
+
+## Fix
+
+Remove line 1:
+```python
+print("Hello World")
+```
+
+## Files
+- `basics/01_introduction/01_hello_world.py`
+
+## Why Important
+
+This is the first program beginners run. Extra output is confusing and looks like a mistake.
+
+## Testing
+```bash
+cd basics/01_introduction
+python 01_hello_world.py
+# Should only output: Hello World
+```

.github/ISSUES_TO_CREATE/004_bug_flask_debug.md

@@ -0,0 +1,45 @@
+---
+title: "BUG: Flask debug mode enabled in production code"
+labels: ["bug", "security", "priority: high"]
+---
+
+## Bug Description
+
+The Flask REST API has debug mode enabled, which is a security risk.
+
+## Problem
+
+In `rest_api/main.py` (line 71):
+```python
+if __name__ == "__main__":
+    app.run(debug=True)  # Security risk!
+```
+
+## Security Risk
+
+Debug mode allows:
+- Interactive code execution
+- Detailed error exposure
+- Should NEVER be in production
+
+## Fix
+
+Use environment variable:
+
+```python
+import os
+
+if __name__ == "__main__":
+    debug = os.environ.get("FLASK_DEBUG", "False").lower() == "true"
+    app.run(debug=debug)
+```
+
+## Files
+- `rest_api/main.py`
+
+## Testing
+```bash
+cd rest_api
+python main.py
+# Should run with debug=False by default
+```

.github/ISSUES_TO_CREATE/005_bug_guess_number_crash.md

@@ -0,0 +1,45 @@
+---
+title: "BUG: Guess number game crashes on non-integer input"
+labels: ["bug", "good first issue"]
+---
+
+## Bug Description
+
+The guess number game crashes when user enters non-integer input.
+
+## Problem
+
+In `basics/11_projects/01_guess_number.py`:
+```python
+user_input = int(input(f"Guess the Number: "))  # Crashes on "abc"
+```
+
+## Error
+
+```
+ValueError: invalid literal for int() with base 10: 'abc'
+```
+
+## Fix
+
+Add input validation:
+
+```python
+while True:
+    try:
+        user_input = int(input(f"Guess the Number: "))
+        break
+    except ValueError:
+        print("Please enter a valid number!")
+```
+
+## Files
+- `basics/11_projects/01_guess_number.py`
+
+## Testing
+```bash
+cd basics/11_projects
+python 01_guess_number.py
+# Enter "abc" → should show error, not crash
+# Enter "50" → should work normally
+```

.github/ISSUES_TO_CREATE/006_bug_rock_paper_crash.md

@@ -0,0 +1,45 @@
+---
+title: "BUG: Rock paper scissors crashes on invalid input"
+labels: ["bug", "good first issue"]
+---
+
+## Bug Description
+
+The rock paper scissors game crashes or behaves unexpectedly on invalid input.
+
+## Problem
+
+In `basics/11_projects/03_rock_paper_scissors.py`:
+- No input validation
+- Assumes user enters "rock", "paper", or "scissors"
+
+## Expected
+
+Should handle invalid input gracefully:
+```
+Enter your choice (rock/paper/scissors): dragon
+Invalid choice! Please enter rock, paper, or scissors.
+```
+
+## Fix
+
+Add input validation loop:
+
+```python
+while True:
+    user = input("Enter your choice (rock/paper/scissors): ").lower()
+    if user in ["rock", "paper", "scissors"]:
+        break
+    print("Invalid choice! Try again.")
+```
+
+## Files
+- `basics/11_projects/03_rock_paper_scissors.py`
+
+## Testing
+```bash
+cd basics/11_projects
+python 03_rock_paper_scissors.py
+# Enter "dragon" → should show error message
+# Enter "rock" → should work normally
+```

.github/ISSUES_TO_CREATE/007_cleanup_duplicates.md

@@ -0,0 +1,48 @@
+---
+title: "CLEANUP: Remove duplicate Python files in basics/"
+labels: ["cleanup", "good first issue"]
+---
+
+## Issue
+
+Many directories have duplicate files - same code exists twice with different names.
+
+## Example
+
+In `basics/01_introduction/`:
+- `01_hello_world.py` 
+- `hello_world_first.py` ← Duplicate
+
+This pattern exists across all basics folders (~110 duplicate files total).
+
+## Problem
+
+- Confusing for learners (which file to run?)
+- Harder to maintain
+- Bloated repository
+
+## Fix
+
+Keep only numbered files (e.g., `01_*.py`), delete descriptive names.
+
+## Files to Check
+
+| Directory | Duplicates |
+|-----------|------------|
+| 01_introduction | 2 |
+| 02_variables_types | 13 |
+| 03_control_flow | 10 |
+| 04_functions | 11 |
+| 05_data_structures | 21 |
+| 06_strings | 8 |
+| 07_file_handling | 13 |
+| 08_oop | 15 |
+| 10_advanced | 11 |
+| 11_projects | 6 |
+
+## Testing
+After cleanup, verify README examples still work:
+```bash
+cd basics/01_introduction
+python 01_hello_world.py  # Should still work
+```

.github/ISSUES_TO_CREATE/008_cleanup_pycache.md

@@ -0,0 +1,41 @@
+---
+title: "CLEANUP: Remove __pycache__ folders and .pyc files"
+labels: ["cleanup", "good first issue"]
+---
+
+## Issue
+
+Repository contains `__pycache__` folders and `.pyc` files that should be in `.gitignore`.
+
+## Problem
+
+These are auto-generated Python bytecode files:
+- Not needed in repository
+- Increase repo size
+- Can cause confusion
+
+## Fix
+
+1. Delete all `__pycache__/` folders
+2. Delete all `*.pyc` files
+3. Verify `.gitignore` includes:
+   ```
+   __pycache__/
+   *.pyc
+   *.pyo
+   .venv/
+   ```
+
+## Command to Clean
+
+```bash
+# Find and remove all __pycache__ folders
+find . -type d -name "__pycache__" -exec rm -rf {} +
+
+# Find and remove all .pyc files
+find . -name "*.pyc" -delete
+```
+
+## Prevention
+
+Update `.gitignore` if not already present.