Resolving the latest directory data…

Loading page

smithers.directory

An independent index for discovering Smithers workflows from GitHub. Detail pages resolve live source; publishers and workflow behavior are not security audited.

Directory Use workflows Publish Add repository GitHub Smithers

Compatible with Smithers · independently operatedInspect live source and preview the file plan before installing

directory

ralfboltshauser/ralf-workflows

lighthouse-check

WorkflowReview before install

lighthouse-check

Run local and optional production Lighthouse checks, review artifacts and codebase context, and produce a reviewed remediation report.

Repository: ralfboltshauser/ralf-workflows
Installs: 12
Source ref: HEAD
Current mutable ref · contents may change upstream

Start with the source

This is the entry file Smithers will copy for the selected workflow. Read it at the same ref shown above before trusting it.

.smithers/workflows/lighthouse-check.tsxOpenworkflow source on GitHub

This page could not resolve an immutable commit. The link and install command follow HEAD, so review again if upstream changes.

Planned file mappings

Each repository source maps to a local destination. Installing fetches and copies this plan; it does not execute the files. Explicit support paths may not be fetched until installation, so verify them in GitHub too.

7 files

Sourcedocs/lighthouse-check.md

Destination.smithers/docs/lighthouse-check.md

02Source.smithers/lib/lighthouse/index.tsDestination.smithers/lib/lighthouse/index.ts

03Source.smithers/lib/lighthouse/lhci.test.jsDestination.smithers/lib/lighthouse/lhci.test.js

04Source.smithers/lib/lighthouse/lhci.tsDestination.smithers/lib/lighthouse/lhci.ts

05Source.smithers/lib/lighthouse/prompts.tsDestination.smithers/lib/lighthouse/prompts.ts

06Source.smithers/lib/lighthouse/schemas.tsDestination.smithers/lib/lighthouse/schemas.ts

07Source.smithers/workflows/lighthouse-check.tsxDestination.smithers/workflows/lighthouse-check.tsx

Claims and code signals

These lists answer different questions. Neither is a security audit, permission boundary, or guarantee of runtime behavior.

Publisher-declared capabilities

Claims written into the manifest by the publisher. They are self-reported and have not been verified.

filesystemshellcodexnetwork

Entry-file heuristic signals

Simple pattern matches in the entry file only. They can miss behavior in dependencies or flag harmless code.

agentapproval

Configuration and labels

Environment keys are names only. This directory never provides or validates their values.

Environment keys

None declared.

Publisher tags

lighthouse
performance
accessibility
seo
web
optimization

Supporting docs

Documentation declared for this workflow is installed with the same workflow selection.

1 doc

Operator guide

How to run local and optional production Lighthouse checks, configure inputs, and keep runs report-only.

Shown after install

docs/lighthouse-check.md.smithers/docs/lighthouse-check.md

Example command

bunx smithers-orchestrator workflow run lighthouse-check --input '{"repoPath":".","localUrl":"http://localhost:3000","routes":["/"],"numberOfRuns":3,"allowImplementation":false}'

Install options

Add this workflow

Start with a preview. Choose a different mode only when you are ready.

No files written

Resolve the selected workflow and print workflow/file counts and requirements without changing your project.

$npx --yes smithers-directory add ralfboltshauser/ralf-workflows@lighthouse-check --dry-run

This command follows the repository's current mutable ref. Preview it again if the source changes.

The @lighthouse-check selection keeps this workflow's support files and docs with it.

Copying this command does not run it. Running the install copies files; it does not execute the workflow.