fec-dependency-upgradeUse when diagnosing frontend build failures, runtime errors, UI anomalies, API/data problems, white screens, request failures, or unexplained production exceptions; Chinese triggers include debugging, debug, troubleshooting, positioning, error reporting, exceptions, white screens, request failures.
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-dependency-upgradeGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Nov 16, 2026 · audit v1.0
Generated Nov 16, 2026
When a deployed front-end app shows a blank screen or throws unexplained exceptions in production, on-call engineers use this skill to classify the fault as runtime or api, collect console stacks and state snapshots, and test up to three ranked hypotheses. That keeps the fix minimal and evidence-backed instead of guess-driven hotfixes.
When CI builds exit non-zero due to type errors, import resolution issues, or peer dependency conflicts, teams apply the build module to capture minimal failing commands and compare Node/package-manager versions across CI environments. The workflow also redirects true dependency-version work to the separate upgrade process.
When requests return unexpected status codes or UI data looks stale or inconsistent, developers use the api module to inspect request URLs, payloads, interceptor chains, and cache race conditions. curl reproduction and mock layering isolate whether the fault lives in the frontend, middleware, or backend.
After a styling refactor ships, visual deviations and broken responsive layouts get categorized under the ui module. Engineers diff screenshots against desired states, inspect computed styles and specificity conflicts, and verify across breakpoints in DevTools before touching shared styles.
After a fault is resolved, the skill produces a timestamped markdown diagnostic report covering issue type, evidence, hypothesis verification records, root cause, minimal fix, and residual risk. This gives teams a consistent artifact for reviews and knowledge sharing across builds, runtime, UI, and API issues.
Sell an error-tracking and session-replay platform whose alert triage flows mirror this classify-collect-hypothesize framework. The skill encodes and automates the diagnostic methodology inside the product UI and in-app AI assistants.
Distribute the skill as a built-in debugging copilot in an IDE or AI coding assistant, automating evidence collection and review of the hypotheses it generates. Upsell autonomous triage and infrastructure access.
Agencies use the skill to standardize incident triage and reports across client engagements, and can resell it as diagnostic audits with per-incident SLAs. The structured report format underpins verified outcomes that justify premium rates.
💬 Integration Tip
Wire the skill into incident-response playbooks and error-tracking or IDE assistants so triage evidence is collected automatically, and enforce the report-template output in postmortem workflows to keep fixes minimal and auditable.
Scored Nov 16, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.