repo-config

Resolve default branch, repository owner/name, and branch conventions via gh repo view.

6|2|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/synaptiai/synapti-marketplace --skill repo-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-config
Source: https://github.com/synaptiai/synapti-marketplace/tree/main/plugins/gh-workflow/skills/repo-config
Command: npx skills add https://github.com/synaptiai/synapti-marketplace --skill repo-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides dynamic repository configuration patterns for gh-workflow agents. Use when an agent needs the default branch name for diffs, the repository owner/name for API calls, or branch naming and commit conventions for validation.

Core Features & Use Cases

  • Detects default branch via gh repo view for diffs.
  • Resolves repository owner/name for GitHub API calls.
  • Validates and applies branch naming conventions via project settings.

Quick Start

Ask the agent to determine the repository default branch, the owner/name, and recommended branch conventions for your project.

Frequently Asked Questions about repo-config

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

FAQPage Schema
How do I find the default branch name for a GitHub repository using gh?

Find the default branch name for a GitHub repository by running gh repo view to fetch and resolve the target baseline dynamically for code reviews and CI diff automation.

How do I get the repository owner and name for GitHub API calls?

Get the repository owner and name for GitHub API calls by resolving the nameWithOwner configuration dynamically, providing the exact identity needed for multi-repo project automation pipelines.

Can I enforce branch naming conventions across multi-repo GitHub projects?

You can enforce branch naming conventions across multi-repo GitHub projects by applying configurable validation rules from project settings to standardize branch types and commits for gh-workflow agents.

What is dynamic repository context detection for gh-workflow agents?

Dynamic repository context detection for gh-workflow agents is the automated resolution of default branches, repository identities, and branch conventions to support CI pipelines and API calls.

Does repo-config work with multi-repo GitHub automation pipelines?

Repo-config works with multi-repo GitHub automation pipelines by applying repository identity resolution and branch validations across multiple projects to support consistent CI and code review workflows.

Why do I need to resolve the default branch for GitHub diffs in CI?

You need to resolve the default branch for GitHub diffs in CI to establish an accurate baseline for code reviews, ensuring automated pipelines fetch correct target branches via gh repo view.