github-release-briefing-skill

Featured

Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.

Code & Development 2,382 stars 262 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
56
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /github-release-briefing-skill Create a current briefing for the latest published release of one public GitHub repository. Run `scripts/run_pipeline.py` with an `OWNER/REPOSITORY` input. The command uses GitHub's public REST endpoint, writes a Markdown briefing, and does not authenticate, publish, modify a repository, or download release assets. ```bash python3 scripts/run_pipeline.py --repository openai/openai-python --output release.md ``` ## Required behavior 1. Reject malformed repository identifiers before any request. 2. Retrieve only the latest published release and identify its tag, title, date, and URL. 3. State clearly when a repository has no published release or is unavailable. 4. Include the GitHub API source URL so a human can inspect the result. ## Gotchas - A GitHub "latest" release excludes drafts and prereleases according to the API's rules. - This is dependency-awareness evidence, not a change-approval recommendation. - Public API availability and release content can change after retrieval. ## References - https://docs.github.com/en/rest/releases/releases#get-the-latest-release

Details

Author
FrancyJGLisboa
Repository
FrancyJGLisboa/agent-skills-platform
Created
10 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category