$ loading_
Watch file changes and automatically rebuild across any language or build system.
The materials indicate a local file-watching and auto-rebuild utility with no declared secrets or remote endpoints. No clear high-risk red flags are present, but its local build-triggering and file-monitoring behavior still warrants normal caution as a local automation tool.
The materials explicitly state that no keys or environment variables are required, and there is no request for API tokens, account credentials, or other sensitive authentication data, so credential exposure risk appears low.
No remote endpoints or networking requirements are declared; the README only describes local watching and rebuilding, with no indication that user data is sent to third-party services.
The description says it can 'watch and run builds,' indicating that it is intended to trigger local build commands or related processes on the host. This is a normal capability for such tools, but you should still verify what build scripts or commands it actually runs.
As a file-watching and auto-rebuild tool, its normal operation requires observing local file changes and may indirectly read or write project artifacts or working-directory contents. The materials do not show requests for access beyond that purpose, but it should still be limited to the minimum necessary directories.
A positive factor is that it is open source on GitHub and the source is auditable; however, the repository has 0 stars, unknown maintenance status, and no declared license, which weakens community validation and governance signals. Supply-chain trust is therefore only moderate, and source review is advisable before adoption.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "poltergeist" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/nix-openclaw-tools/main/tools/poltergeist/skills/poltergeist/SKILL.md 2. Save it as ~/.claude/skills/poltergeist/SKILL.md 3. Reload skills and tell me it's ready
Help me configure poltergeist for a Node.js frontend project. Watch the src and public folders, and automatically run npm run build whenever files change. Also explain the startup command.
A sample watcher configuration for the frontend project and instructions for starting the auto-rebuild workflow.
I have a project with a Go backend and Sass styles. Design a poltergeist configuration so that backend code changes run go build, and style file changes run Sass compilation. Specify the watch paths for each.
An auto-watch and rebuild setup for a multi-language project, including build commands mapped to different directories.
Design a poltergeist-based automation setup for my local development environment. Watch source code, test config, and static assets, and run build, test, or asset bundling commands after changes. Include the configuration approach.
A watcher-based automation plan that improves local development productivity, clearly mapping change types to triggered commands.
Use the poltergeist and polter CLIs to watch and run builds.
Example:
Mirror Discord history into SQLite for offline search, analysis, and reporting.
Search places, details, and reviews via Google Places with human or JSON output.
Search Markdown knowledge bases, notes, and docs to quickly find needed information.
Search local WhatsApp Desktop chats, messages, and media metadata read-only.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Log build progress safely to ThePuffer tracker for shared project visibility.
Automatically resolves Git merge conflicts so agents handle only complex hunks.
Wait for or emit local dev events without polling for automation workflows.
Monitor website changes and trigger automated follow-up workflows via MCP.
Detect duplicated code across many formats to improve code quality and refactoring.
AI tool for inspecting, editing, validating, and automating Godot 4 projects.