working-tree-governorGovern dirty git working trees by classifying runtime noise vs real source changes, defaulting to selective staging, verifying staged scope, and asking the o...
Install via ClawdBot CLI:
clawdbot install lobsterquant/working-tree-governorGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 11, 2026
Before a critical deployment, the repo is cluttered with logs, runtime state, and generated artifacts. The skill helps isolate only the intentional code changes, ensuring a clean, reviewable commit that doesn't accidentally deploy old state files or logs.
A developer has been iterating on a feature, generating debug logs and cached binaries. Instead of stashing everything or committing all noise, the skill classifies files and selectively stages only the relevant source and test changes.
After debugging a live incident, the workspace contains forensics snapshots, temporary state dumps, and quick fixes. The skill ensures only the actual fix and related tests are committed, preserving forensics for analysis but excluding them from version control.
A contributor makes changes alongside CI artifacts and local configs. The skill helps them commit only the intended code changes, avoiding blowing up the PR with unrelated generated files.
In a machine learning project, raw data, model checkpoints, and experiment logs clog the workspace. The skill distinguishes between authored code (features, tests) and generated outputs (results, caches), committing only the former.
Offer the skill as part of a larger AI-assisted development platform. Revenue comes from monthly subscriptions for teams that want to reduce commit noise and prevent bad commits.
Licensed to enterprises that need audit-trail quality commits. The skill ensures no accidental inclusion of logs, state, or binaries in commits, meeting compliance standards. Revenue from per-seat licenses.
Free basic version covers common noise files; paid version adds custom bucket definitions, policy enforcement, and integration with CI/CD pipelines. Revenue from premium upgrade and consulting.
💬 Integration Tip
Add the skill as a pre-commit hook or a command alias; the heuristic file patterns can be customized in a JSON config file to match your repo's layout.
Scored May 11, 2026
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation".
Local-first recurring schedule engine for reminders, repeated tasks, and time-based execution plans. Use whenever the user mentions recurring timing, repetit...
Create, list, modify, and remove scheduled cron jobs to automate system tasks using simplified cron syntax and manage output logging.
Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.
Diagnose and triage cron job failures. Checks job states, identifies error patterns, prioritizes by criticality, generates health reports. Triggers on: cron...
Decomposes complex user requests into executable subtasks, identifies required capabilities, searches for existing skills at skills.sh, and creates new skills when no solution exists. This skill should be used when the user submits a complex multi-step request, wants to automate workflows, or needs help breaking down large tasks into manageable pieces.