Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized utilities for managing the transition from development to deployment. It helps developers synthesize technical commit histories into clear App Store changelogs and deploy multi-agent swarms to diagnose regressions without altering code.
WHO IT'S FOR
iOS developers
automate App Store release notes generation
iOS QA / test automation engineers
debug iOS apps on booted simulators
Backend / infrastructure engineers
perform multi-agent root-cause investigation for bugs
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Use the app-store-changelog skill to inspect the git history in <repository-path> since <tag-or-ref>, identify only user-visible changes, and draft 5–10 concise App Store “What's New” bullets. Treat <repository-path> and <tag-or-ref> as placeholders for the actual repository and release range; if the ref is omitted, use the last tag as documented. Do not publish the notes.
Use the github skill to investigate the failing CI checks for pull request <pr-number> in <owner/repo>. Identify the relevant failed workflow run, inspect its failed-step logs, and summarize the likely failure without changing the pull request or repository. Replace <pr-number> and <owner/repo> with the actual pull-request number and repository name.
Use the react-component-performance skill to review <component-path> and the slow interaction described in <slowdown-description>. Identify the most likely re-render churn or expensive render work, then recommend one targeted optimization and a small React DevTools Profiler validation step. Treat both angle-bracketed values as placeholders. Do not edit the code yet.
Codex