slop-scan-now

Trigger a slop code quality scan via D-Bus and output results.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill slop-scan-now
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slop-scan-now
Source: https://github.com/dmzoneill/skills/tree/main/slop-scan-now
Command: npx skills add https://github.com/dmzoneill/skills --skill slop-scan-now

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of triggering a code quality scan using the slop daemon, ensuring your code is checked before fixes are applied.

Core Features & Use Cases

  • On-demand Scanning: Initiate a code quality scan whenever needed.
  • Daemon Integration: Communicates with a running slop daemon via D-Bus.
  • Configurable Wait Time: Option to wait for the scan to complete, with a configurable timeout.
  • Use Case: When you've made changes to your code and want to see the latest quality metrics before attempting to fix them, you can use this skill to trigger an immediate scan.

Quick Start

Trigger a slop code scan now and wait for it to complete.

Frequently Asked Questions about slop-scan-now

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

FAQPage Schema
How do I trigger an on-demand code quality scan via a daemon?

To trigger a code quality scan, the skill sends a 'scan_now' command via D-Bus to a running daemon. It checks the daemon status, initiates the scan, and optionally waits for completion with a configurable timeout.

Can I wait for a code quality scan to finish before checking metrics?

Yes, you can configure a wait timeout when triggering the code quality scan. The skill sends the scan command via D-Bus and waits for the daemon to complete the process before outputting the scan results and statistics.

How do I check if the slop daemon is running before initiating a scan?

The skill checks the daemon's status automatically before sending the 'scan_now' command. It verifies the D-Bus connection to the running daemon and logs the session before attempting to trigger the code quality scan.

Does triggering a D-Bus scan require a specific environment setup?

Triggering a D-Bus scan requires a running slop daemon to communicate with. The skill depends on the D-Bus protocol to send the 'scan_now' command and retrieve code quality metrics from the active daemon session.

What is the best way to automate code quality checks before applying fixes?

Automating code quality checks involves triggering a scan via D-Bus to a running daemon to retrieve current metrics. This ensures your code is checked before fixes are applied, providing updated statistics and scan results on demand.