skills.rest
bketelsen
bketelsenCOMMUNITY
Explore all skills by this author →
Website𝕏@bketelsenGitHub

cron-pull-weeds

Automate scheduled weed management with gated PR creation for ytsejam.

Updated Aug 27, 2026
Search Tags:#automation#git#workflow#safety#subagent#pr#cron
One-click install
npx skills add https://github.com/bketelsen/ytsejam --skill cron-pull-weeds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cron-pull-weeds
Source: https://github.com/bketelsen/ytsejam/tree/main/server/skills/cron-pull-weeds
Command: npx skills add https://github.com/bketelsen/ytsejam --skill cron-pull-weeds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This cron-driven skill provides automated weed-pulling for ytsejam by wrapping the /pull-weeds Phase 1-4 with cron-specific safety rules, ensuring unsupervised operation never performs destructive actions.

Core Features & Use Cases

  • Cron-driven bed checks and per-issue dispatch with gate-based safety.
  • Phase-based workflow: Bed check, per-issue PR creation, digest reporting; includes explicit safety divergences like halting on blockers and avoiding merges.
  • Scope: ytsejam only; multi-project support is out of scope, with robust audit trails and recoverable state.

Quick Start

Schedule the cron-pull-weeds workflow to automatically assess weed issues and open gated PRs for ytsejam, followed by a digest report.

Frequently Asked Questions about cron-pull-weeds

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

FAQPage Schema
How do I automate scheduled GitHub issue resolution with cron?▼

Automate scheduled GitHub issue resolution by evaluating open weed issues and dispatching per-issue PRs using cron-driven triggers with strict safety gates to prevent destructive actions.

How does the weed pulling workflow handle unsupervised PR creation safely?▼

Weed pulling workflow ensures unsupervised PR creation safety by applying deterministic gate behavior, halting on blockers, and avoiding merges to guarantee only non-destructive actions execute.

Do I need GitHub CLI access to run automated weed management workflows?▼

Yes, GitHub CLI access is required to run automated weed management workflows, as the cron-driven skill dispatches gated PRs and performs bed checks against the repository scope.

Can I use cron-driven weed pulls for multiple project scopes?▼

No, cron-driven weed pulls are scoped strictly to the ytsejam project scope; multi-project support is out of scope and not supported by the current workflow.

What happens when the automated weed pulling workflow encounters a blocker?▼

When the automated weed pulling workflow encounters a blocker, it halts operation immediately as an explicit safety divergence to prevent destructive actions and maintain recoverable state.

What is the best way to track automated PR creation results from cron jobs?▼

Track automated PR creation results through a digest summary report generated at the end of the workflow, providing robust audit trails and recoverable state for the dispatched PRs.

Related Skills

Explore More Software Engineering Skills→
wiggitywhitneywiggitywhitney

prds-get

Retrieves open GitHub issues labeled PRD with JSON metadata via the GitHub CLI.

Community
Advanced
DeliciousHouseDeliciousHouse
2

aries_integrations_sync

Execute Aries integrations synchronization workflows and report status, errors, and next steps.

Community
Intermediate
tuanemuytuanemuy

issue-implement

Automate GitHub issue execution from planning to PR review.

Community
Advanced
CruxExpertsCruxExperts
3

ls-unfuck-my-git-state

Diagnose broken Git state and generate guided repair plans.

Community
Advanced