Process GitHub issues overnight using time-aware merge rules from .keel/project.yaml.
npx skills add https://github.com/berkayturanci/keel --skill keel-overnight
Please help me install this Agent Skill. Skill: keel-overnight Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-overnight Command: npx skills add https://github.com/berkayturanci/keel --skill keel-overnight
This Skill automates the unattended overnight work block, running a set of predefined commands to process GitHub issues without manual intervention, ensuring continuous progress and a time-aware merge mode.
.keel/project.yaml.Run the keel overnight command to initiate the unattended overnight work block.
High-intent search queries and answers about installing and using this skill.
You can automate unattended overnight GitHub issue processing by executing predefined commands over the queue without manual intervention, ensuring continuous progress during CI/CD workflows. This Skill runs that exact work block until the merge window closes.
Time-aware merge mode is a mechanism keyed on a specific merge window, enabling the merging of pull requests based on the time window. It ensures automated merges only occur during approved hours for unattended overnight work blocks.
To set up automated overnight GitHub work, you must define project-specific values in a `.keel/project.yaml` configuration file. This approach keeps the automation project-neutral by reading all necessary settings from that YAML file.
Yes, you need keel-core to run unattended overnight work automation. The Skill requires keel-core as a dependency alongside project-specific `.keel/project.yaml` configurations to properly execute continuous integration and delivery workflows.
Yes, you can get a report of automated GitHub issue processing after an overnight block. The automation generates a session and morning report summarizing all the work completed during the unattended overnight execution.
You should not use unattended overnight merge automation if your GitHub project lacks predefined `.keel/project.yaml` configurations or if your CI/CD workflows require manual intervention rather than time-aware merge windows for pull requests.
berkayturanciAutomate GitHub issue lifecycle from intake to merge using keel workflows.
Quriosity-agentOrchestrates parallel AI agents for automated GitHub issue resolution, CI monitoring, and PR reviews via the qagent CLI for Qcut development.
awinogradovSelect and activate an open GitHub or Linear issue for autopilot processing.
mfittkoAutomate GitHub issue-to-merged PR workflows through seven deterministic phases.