Automated summary
Analyzes and summarizes the status of a GitHub milestone by version number, or lists all open milestones.
Strengths
- Structured report with issue progress (open/closed)
- Automatic mode detection (status vs list)
- Extraction of key issues marked with 🎯 emoji
- Native GitHub API usage for up-to-date data
Limitations
- Limited to the `zeroae/zae-limiter` repository (specific fork)
- Requires a GitHub token with milestone access
- No support for closed milestones in list mode
When you need to check the progress of an upcoming release or list open milestones in a repository.
If the repository does not follow the 'v' version convention or if you need historical data on closed milestones.
Security analysis
SafeThis skill only uses read-only GitHub CLI commands (gh api, gh issue list, gh issue view) against a specific repository. There is no execution of arbitrary code, network requests outside GitHub's API, or modification of data. The allowed tools are non-destructive and safe for automated use.
No concerns found
How this analysis is madeExamples
/milestone 1.0.0/milestone listdescription: When users mention a milestone version (e.g., "0.4.0", "v0.4.0") or ask about release status, invoke this skill to analyze GitHub milestone progress, issues, and suggest next steps. argument-hint: [version] | list allowed-tools: Bash(gh api:), Bash(gh issue list:), Bash(gh issue view:*) context: fork model: haiku
Milestone Skill
Analyze and summarize GitHub milestone status.
Modes
| Mode | Trigger | Purpose |
|------|---------|---------|
| Status | /milestone 1.0.0, /milestone v0.7.0 | Analyze specific milestone |
| List | /milestone list, /milestone (no args) | Show all open milestones |
Mode Detection
- If version number provided (e.g.,
1.0.0,v0.7.0,0.5) → Status mode - If
listkeyword → List mode - If no arguments → List mode
Status Mode
Extract the version from the user input. Normalize it (add "v" prefix if missing, e.g., 1.0.0 → v1.0.0).
Run these commands (replace VERSION with the normalized version):
Step 1: Get milestone details:
gh api repos/zeroae/zae-limiter/milestones --jq '.[] | select(.title == "VERSION") | {title, description, state, open_issues, closed_issues}'
Step 2: List all issues:
gh issue list --milestone "VERSION" --state all --json number,title,state,labels --jq '.[] | "\(.state)\t#\(.number)\t\(.title)"'
Step 3: If any issue title starts with "🎯", get its body:
gh issue view <number> --json title,body
See status.md for output format.
List Mode
Run this command:
gh api repos/zeroae/zae-limiter/milestones --jq '.[] | "- \(.title): \(.description)"'
Output the results.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/github-milestone-analyzer-mm78nmws/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/github-milestone-analyzer-mm78nmws' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-milestone-analyzer-mm78nmws/download' --output '.skill-downloads/github-milestone-analyzer-mm78nmws/SKILL.md.part' && mv '.skill-downloads/github-milestone-analyzer-mm78nmws/SKILL.md.part' '.skill-downloads/github-milestone-analyzer-mm78nmws/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/github-milestone-analyzer-mm78nmws/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.