manifest

Scan remote GitHub PRs and feature branches to generate a consolidated status report.

4|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill manifest-highflame-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifest
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/manifest
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill manifest-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, awk, grep, sed.

What problem does it solve?

This skill solves the visibility gap in collaborative AI-assisted development by providing a unified, remote-derived view of all active work across different sessions and machines.

Core Features & Use Cases

  • Cross-Session Tracking: Aggregates open PRs and pushed feature branches to show what every collaborator is currently working on.
  • Conflict Awareness: Identifies coarse overlaps in components or domains to prevent redundant work or merge conflicts before they happen.
  • Use Case: Before starting a new feature, run this to see if another agent session is already modifying the same component, allowing you to coordinate or sequence your efforts.

Quick Start

Run the manifest skill to generate a report of all current in-flight work and potential component overlaps.

Frequently Asked Questions about manifest

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

FAQPage Schema
How do I track in-flight GitHub PRs and feature branches across multiple agent sessions?

Tracking in-flight GitHub PRs across distributed agent sessions requires read-only analysis of remote repository state and pull request metadata. This skill aggregates open PRs and pushed feature branches to generate a consolidated cross-session status report.

What is the best way to prevent merge conflicts in collaborative AI-assisted development?

Preventing merge conflicts in collaborative AI development requires identifying coarse overlaps in components or domains across active work. This skill scans remote GitHub PRs and feature branches to detect potential component overlaps for proactive coordination before conflicts happen.

Do I need the GitHub CLI to monitor remote repository state and pull request metadata?

Yes, monitoring remote repository state and pull request metadata requires the GitHub CLI and git installed. This skill uses these dependencies to perform read-only analysis of repository state and aggregate open PRs across distributed sessions.

How does cross-session visibility work for distributed agent development workflows?

Cross-session visibility for distributed agent workflows works by scanning remote GitHub PRs and pushed feature branches to show what every collaborator is currently working on. It operates across different machines to provide a unified, remote-derived view of all active development.

Does this PR tracking approach support identifying component overlaps before starting a new feature?

Yes, this PR tracking approach supports identifying component overlaps by scanning remote GitHub PRs and feature branches before you start new work. It detects coarse overlaps in components or domains so you can coordinate or sequence your efforts proactively.

Are there limitations to using remote-derived repository state for conflict awareness?

A limitation of using remote-derived repository state for conflict awareness is that it only identifies coarse overlaps in components or domains, not granular line-level conflicts. It requires pushed feature branches and open PRs to exist on GitHub to aggregate current in-flight work.