ghp:init

Automate GitHub session triage using gh project, milestone, issue, and PR lists.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/fredericosantos/skills --skill ghp-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghp:init
Source: https://github.com/fredericosantos/skills/tree/main/skills/ghp/commands/init
Command: npx skills add https://github.com/fredericosantos/skills --skill ghp-init

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Start a development session on a repository to quickly surface active work, blockers, and next steps, then guide you to choose whether to start new work, resume existing efforts, or organize issues.

Core Features & Use Cases

  • Auto-fetches project data: projects, milestones, open issues, and open PRs from the repository.
  • Provides a concise activity summary and guided decision prompts for planning work.
  • Supports triage: creates or links a project if none exists, and routes tasks to subagents for issue creation or organization.

Quick Start

Run ghp:init in your repository to start a new development session and review the current state.

Frequently Asked Questions about ghp:init

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

FAQPage Schema
How do I triage GitHub issues and milestones at the start of a development session?

To triage GitHub issues at the start of a session, run the initialization command in your repository to auto-fetch active projects, milestones, open issues, and PRs. It provides a concise activity summary and guided prompts to help you choose whether to start new work, resume tasks, or organize issues.

What is the best way to surface blockers and active work in a GitHub repository?

Surfacing blockers and active work involves fetching current repository state data via gh project, milestone, issue, and pr list commands. This process detects git repository state and guides your choices by providing a concise activity summary of active items and next steps for your development workflow.

Can I automate GitHub project management and issue triage using CLI tools?

Yes, you can automate GitHub project management and issue triage using CLI tools. This Skill fetches project data via gh project list and git commands, guiding decisions to create new work, resume existing tasks, or organize issues while creating or linking a project if none exists.

Do I need the gh CLI installed to fetch GitHub repository state for project management?

Yes, you need the gh CLI and git installed to fetch GitHub repository state for project management. The Skill depends on these tools to execute commands like gh issue list and gh pr list, which retrieve the active items, milestones, and PRs needed to triage your work session.

How does issue triage work when no GitHub project board exists for a repository?

When no GitHub project board exists, the triage process creates or links a project automatically. It then routes tasks to subagents for issue creation or organization, ensuring your development workflow can proceed with structuring and managing open items effectively.

What are the limitations of using automated CLI scripts for GitHub issue triage?

The limitations of using automated CLI scripts for GitHub issue triage include reliance on gh and git dependencies for data fetching. The process focuses on surfacing active items and guiding decisions, but actual issue creation or organization is routed to subagents rather than handled inline.