project-pulse

Generate planning artifacts from GitHub issues and PRs.

132|13|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/holon-run/holon --skill project-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-pulse
Source: https://github.com/holon-run/holon/tree/main/skills/project-pulse
Command: npx skills add https://github.com/holon-run/holon --skill project-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates PM synchronization by turning GitHub issue and PR state into a concise planning view that guides controller actions.

Core Features & Use Cases

  • GitHub-first sync and local cache for issues and PRs.
  • Generates planning artifacts: report.json, report.md, and sync-state.json for decisive actions.
  • Provides next_actions and recommendations to drive automated or semi-automated planning.

Quick Start

Run the project-pulse pulse script to generate the latest PM pulse artifacts for your repository.

Frequently Asked Questions about project-pulse

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

FAQPage Schema
How do I generate project management plans from GitHub issues and pull requests?

To generate project management plans from GitHub issues, you can use a script-driven workflow that reads repository data, caches it locally, and outputs planning-ready artifacts like report.json and report.md. This automates PM synchronization.

Can I sync GitHub issues into a planning view for daily or weekly priority tracking?

Yes, you can sync GitHub issues into a planning view designed for daily or weekly priority syncing. The process reads GitHub issue and PR state locally, generating a concise report to guide controller actions and planning.

Do I need GitHub CLI and jq installed to automate issue tracking and reporting?

Yes, you need the GitHub CLI (gh) and jq installed as dependencies to automate issue tracking and reporting. These tools facilitate reading repository data and processing the JSON structures needed for local caching.

What is the best way to automate PM synchronization across GitHub-first projects?

The best way to automate PM synchronization across GitHub-first projects is running a script-driven workflow that caches GitHub data locally. It generates report.json, sync-state.json, and report.md, providing next_actions for decisive planning.

Does this GitHub reporting workflow provide recommendations for automated planning?

Yes, this GitHub reporting workflow provides next_actions and recommendations to drive automated or semi-automated planning. It transforms issue and PR state into planning artifacts that guide controller actions.

What output formats are generated when syncing GitHub issues for project management?

Syncing GitHub issues for project management generates report.json, report.md, and sync-state.json. These files provide structured data, readable summaries, and local cache state for planning-ready artifacts.