Retrieve labels from a GitHub repository, filter their names by partial matches, and choose page sizes and page numbers. Results arrive as JSON, including label names, colors, descriptions, and pagination details.
List GitHub repository labels with per_page pagination and name filtering support.
Review the instructions the agent will receive before you install.
List GitHub repository labels with efficient pagination using the --per-page flag.
Use this script to list labels from any repository with controlled page sizes.
./query-labels.sh --owner github --repo gh-aw
# Returns 10 labels (default per_page=10)
# Get the first label only
./query-labels.sh --owner github --repo gh-aw --per-page 1
# Get 25 labels starting from page 2
./query-labels.sh --owner github --repo gh-aw --per-page 25 --page 2
# Only labels whose name contains "bug" (case-insensitive)
./query-labels.sh --owner github --repo gh-aw --name-filter bug
When --name-filter is set, all labels are fetched and filtered, then
--per-page/--page are applied to the filtered results.
| Parameter | Required | Default | Description |
|---|---|---|---|
--owner | Yes | - | Repository owner (username or organization) |
--repo | Yes | - | Repository name |
--per-page | No | 10 | Results per page (1–100) |
--page | No | 1 | Page number |
--name-filter | No | - | Case-insensitive substring filter on the label name |
Returns JSON with the following fields:
{
"labels": [
{
"id": 12345,
"node_id": "LA_...",
"url": "https://api.github.com/repos/owner/repo/labels/bug",
"name": "bug",
"color": "d73a4a",
"default": true,
"description": "Something isn't working"
}
],
"item_count": 10,
"per_page": 10,
"page": 1
}
Calls the GitHub REST API:
GET /repos/{owner}/{repo}/labels?per_page={n}&page={n}
When --name-filter is used, the script pages through all labels
(--paginate) before filtering and slicing locally.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.