- Home
- Skills
- Testing & Debugging
- Devsentinel
More screenshots
Works with the AI Agents you already use
Devsentinel
Safe code editing for agents with impact analysis, breaking change detection, and visual regression testing.
$9.99
Devsentinel
Example session with this skill installed
I need to rename the handleAuth function in src/lib/auth.ts. Check the impact and see if it breaks anything before I proceed.
- Read your context and instructions
- Compiled the devsentinel
I have analyzed the blast radius for the handleAuth symbol in src/lib/auth.ts. The scan identified several consumers that will require updates to prevent breaking the build.
Impact Analysis: handleAuth
| Metric | Value |
|---|---|
| Risk Level | High (Risk Score: 58) |
| Direct Consumers | 4 files |
| Transitive Consumers | 2 files via src/lib/index.ts |
| Test Coverage | test/auth.spec.ts, test/integration/login.test.ts |
| Unresolved Imports | None |
Affected Files
src/middleware/session.ts(Lines 12, 45)src/api/routes/login.ts(Line 8)src/components/AuthProvider.tsx(Line 22)src/hooks/useUser.ts(Line 15)
Breaking Change Detection
Running detect_breaking_changes on your proposed rename to processAuthentication confirms a removed-export error. All 6 consuming files listed above will fail to compile unless their import statements and call sites are updated simultaneously.
Next steps
- Create a safety checkpoint using
create_checkpointbefore starting the rename. - Apply the rename and update all 6 consumer files identified in the scan.
- Run the 2 specific test files listed above to verify the fix.
Connects securely to your tools. The creator never sees your data.
About this skill
Coding agents often break complex projects because they lack context on how a single file edit affects the rest of the codebase. DevSentinel provides the missing safety layer for autonomous coding by performing static analysis and visual audits before changes are committed. It identifies every file that imports your target code, detects breaking API changes before they reach the disk, and runs visual regression tests to ensure UI edits do not break layouts.
What it does
- Impact analysis maps the blast radius of any edit to see which consumers and tests are affected.
- Contract validation identifies breaking changes in exported functions, classes, or types before you write to disk.
- Visual regression captures before-and-after screenshots to detect pixel shifts, horizontal overflow, and text overlaps.
- Safe checkpoints creates full-state backups of the workspace to allow instant rollbacks of failed experiments or refactors.
How it works
- Scan the radius by calling
analyze_blast_radiuson a file or specific symbol to identify all direct and transitive dependencies. - Verify the contract using
detect_breaking_changeswith your proposed code to catch signature mismatches before they cause CI failures. - Audit the UI by running
capture_ui_stateto establish a baseline, thendiff_ui_visualsafter the edit to confirm layout integrity. - Manage state through
create_checkpointandrollback_checkpointto safely test risky refactors without touching git history.
Frameworks & tools
This skill interfaces with an MCP server (stdio/JSON-RPC). It supports TypeScript, JavaScript, and Python. Visual audits require Playwright and Chromium.
Why this beats prompting it yourself
Standard LLM prompts cannot accurately track barrel file re-exports five hops deep or perform pixel-by-pixel comparisons of rendered DOM elements. This tool provides deterministic data from the actual filesystem and browser, replacing agent guesswork with verifiable facts.
Use cases
- Refactoring shared utility functions used across a large monorepo.
- Upgrading dependencies or running codemods with a guaranteed safety net.
- Verifying that CSS changes do not cause unintended layout shifts on deep-linked pages.
- Protecting against silent failures in Python keyword arguments during symbol renames.
Known limitations
Supports TS, JS, and limited Python regex scanning. Does not follow tsconfig extends chains or resolve computed dynamic imports. Checkpoints are limited to workspaces under 250MB.
Supports JS, TS, and basic Python. Workspace limit of 250MB for checkpoints. No support for tsconfig extends chains. Visual audits require manual Chromium installation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires