e2ejs

Scan application pages for JavaScript and HTTP errors and iteratively fix them.

1|Updated Apr 25, 2025

Search Tags:#automation #e2e #javascript #webdev #iterative-fix #error-scanning

Ready to run

npx skills add https://github.com/schmalle/secman --skill e2ejs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2ejs
Source: https://github.com/schmalle/secman/tree/main/.claude/skills/e2ejs
Command: npx skills add https://github.com/schmalle/secman --skill e2ejs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end detection and iterative repair of JavaScript and HTTP errors across a full-stack application, reducing manual debugging time.

Core Features & Use Cases

End-to-end error scanning: Launches and monitors the entire dev environment, then scans every page for JS and HTTP errors.
Iterative fix loop: Classifies errors, applies targeted fixes, restarts the backend after each fix, and re-scans until pages are healthy.
On-demand orchestration: Activates both backend and frontend services via dev scripts and supports repeatable workflows when issues arise during development.

Quick Start

Start the e2ejs skill to spin up the development environment, run the JS error scanner, and automatically fix page errors in a loop.

Frequently Asked Questions about e2ejs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically scan and fix JavaScript errors across all pages of my web application?▼

An iterative error scanner launches your backend and frontend dev scripts, navigates every application page to detect JS and HTTP failures, and applies targeted fixes in a loop until all pages load cleanly or the retry budget is exhausted.

How does the iterative fix loop work when resolving frontend JavaScript errors?▼

The iterative fix loop works by classifying detected JS and HTTP errors, applying targeted code fixes, restarting the backend after each correction, and re-scanning all pages until the application loads without errors or the retry limit is reached.

Do I need to manually start my backend and frontend dev scripts before running an end-to-end JavaScript error scan?▼

No, you do not need to manually start dev scripts. The orchestration tool automatically activates both backend and frontend services via dev scripts, executes the JS error scanner, and manages the entire debugging workflow.

What is the best way to handle HTTP and JavaScript errors detected during end-to-end web development?▼

The best way to handle end-to-end JS and HTTP errors is to automate detection and repair by orchestrating the full development environment, scanning every page, iteratively applying fixes, and restarting the backend after each correction.

What happens when the iterative JavaScript error fixer exhausts its retry budget?▼

When the retry budget is exhausted, the iterative fix loop stops attempting further corrections, leaving any remaining unresolved JavaScript or HTTP errors for manual inspection.