Addressed review comments: refactored skills.js and implemented reset

[pavithapari]

Summary [required]

Refactored script.js to improve overall stability and maintainability while keeping the existing structure and behaviour intact. Fixed broken bracket/closure issues in the generated projects rendering and form submission flow, cleaned up nested logic, and improved the reset functionality so filters, selected skills, quick-pick states, and suggestion inputs are properly cleared without leaving stale UI state.

---

Related Issue [required]

Closes #170

---

Type of Change [required]

• Bug fix — resolves a broken behaviour
• Refactor — restructures code without changing behaviour

---

What Was Changed [required]

File	Change made
static/js/script.js	Fixed broken bracket/closure structure in form submission and results rendering logic
static/js/script.js	Refactored nested callbacks with minimal structural changes
static/js/script.js	Improved clear/reset filters functionality for skills, chips, quick-pick states, and suggestions
static/js/script.js	Cleaned up duplicated conditions and inconsistent indentation
static/js/script.js	Preserved existing functionality while improving readability and stability

---

How to Test This PR [required]

1. Clone this branch:

   git checkout fix/script-refactor-reset

2. Install dependencies:

   pip install -r requirements.txt

3. Run the app:

   python app.py

4. Open:

   http://127.0.0.1:5000
   

5. Verify the following:

   • Add skills manually and through quick-pick chips
   • Submit the recommendation form successfully
   • Verify generated projects render correctly
   • Click the "Clear Filters" button and confirm:
     • Form fields reset
     • Skill chips are removed
     • Quick-pick active states are cleared
     • Suggestions disappear
   • Open and close the GitHub modal
   • Test mobile navigation toggle
   • Verify no console errors appear in the browser

6. Run the tests:

   python tests/test_basic.py

Expected output:

27 passed, 0 failed out of 27 tests

---

Test Results [required]

27 passed, 0 failed out of 27 tests

---

Screenshots (if UI change)

Before	After
Reset button left stale selected states	Reset button fully clears form and UI state
Inconsistent generated project rendering	Stable rendering with corrected logic flow

---

Self-Review Checklist [required]

• I have read CONTRIBUTING.md and followed all guidelines
• My branch name follows the convention: feat/, fix/, docs/, data/, style/, test/
• I have run python tests/test_basic.py and all 27 tests pass
• I have run flake8 . locally and there are no errors
• I have not introduced any print() or console.log() debug statements
• Every new function I wrote has a docstring
• I have not modified files outside the scope of the linked issue
• If I changed the UI, I tested it at 375px (mobile) and 1280px (desktop)
• If I added a project to the dataset, it has all required JSON fields

---

Screen.Recording.2026-05-26.201524.mp4

[vercel]

@pavithapari is attempting to deploy a commit to the komalsony234-1530's projects Team on Vercel.

A member of the Team first needs to authorize it.

[pavithapari]

@komalharshita Thanks for the detailed review and feedback.

As suggested in the previous review comments,
#253 (review) this PR is now separated and scoped specifically for the reset button and form state cleanup functionality to reduce regression risk and simplify validation.

This PR is part of addressing the concerns raised in the earlier review regarding:

• tighter PR scoping
• separating unrelated UI fixes
• safer review and testing of shared form logic

Current scope of this PR:

• Reset button functionality improvements
• Clearing selected skill chips correctly
• Resetting quick-pick states
• Clearing autocomplete/suggestion state
• Preventing stale UI state after reset

The unrelated UI/layout and merge-conflict recovery work will be handled in separate PRs.
I Tested this in local Machine with the lasted feted everything looks fine

[pavithapari]

@komalharshita Please review this PR

[komalharshita]

@pavithapari kindly resolve the merge conflicts

[pavithapari]

@pavithapari kindly resolve the merge conflicts

Resolved the Merge Conflicts. Please review it