skills.rest
Atrium-Hermes
Atrium-HermesCOMMUNITY
Explore all skills by this author →
𝕏@atriumhermesGitHub

Feature

Automate feature discovery and delivery across watched repositories with PRs.

Updated Jun 2, 2026
Search Tags:#automation#repository#feature#continuous-delivery#pull-request#repo-management#ai-build
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill feature-atrium-hermes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Feature
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/feature
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill feature-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates multi-repo feature work by iterating the full list of watched repositories and selecting one viable feature per repo to ship in a single run.

Core Features & Use Cases

  • Multi-repo orchestration: processes every repo in memory/topics/watched-repos.md, builds and ships one feature per repo.
  • Smart prioritization: picks ideas from yesterday's repo-actions ideas, open issues labeled ai-build, and memory MEMORY.md to determine what to implement.
  • End-to-end automation: clones each repo, implements the feature, creates a PR, updates memory/logs, and notifies operators on success.

Quick Start

Run the feature skill to build and ship features for all watched repositories.

Frequently Asked Questions about Feature

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

FAQPage Schema
How do I automate feature delivery across multiple repositories in one run?▼

Multi-repo feature delivery automation works by iterating watched repositories, selecting the highest-impact implementable idea per repo, creating feature branches, and opening pull requests in a single execution.

How does continuous delivery select which features to implement from watched repos?▼

Feature selection prioritizes ideas from yesterday's repo-actions, open issues labeled ai-build, and memory priorities to determine the most viable feature to autonomously implement per repository.

Can I limit automated pull request creation to only one specific repository?▼

Yes, automated pull request creation can be limited to a single repository by setting the appropriate variable, which restricts processing to only the first repo instead of all watched repositories.

What is the best way to manage feature branches for autonomous AI builds across repos?▼

Managing feature branches for AI builds requires per-repo isolation during cloning, implementation, and pull request creation to ensure safe concurrent feature shipping across all watched repositories.

Does multi-repo feature orchestration require a specific watched repos file format?▼

Multi-repo feature orchestration requires repositories to be listed in memory/topics/watched-repos.md, which the automation reads to iterate through and process each repository individually.

Why does automated feature shipping update memory logs after opening a pull request?▼

Automated feature shipping updates memory logs and notifies operators upon success to maintain an accurate record of implemented ideas and ensure visibility into completed continuous delivery actions.

Related Skills

Explore More Software Engineering Skills→
swarm-ai-researchswarm-ai-research

Feature

Select and implement one feature per watched repository, creating a PR for each.

Official
Advanced
aeoncity-demoaeoncity-demo

GitHub Monitor

Monitor GitHub repositories for pull requests, issues, and releases.

Community
Intermediate
softmgsoftmg

github-workflow-automation

Automate GitHub Actions workflow generation and CI/CD pipeline management.

Official
Advanced
HigorAlvesHigorAlves
4

workspace-mode

Detect multi-repo workspaces and manage synchronized branching and pull request linking.

Community
Advanced