Loading...
Loading...
Found 2,521 Skills
Evaluate, prepare, and review contributions to GitHub repositories the user does not own, including discussions, issues, private vulnerability reports, and pull requests. Use it when incorporating feedback or findings into a contribution, preparing the next pull request in a contribution series, or making user-requested revisions to an existing pull request, including maintainer feedback after submission. Do not use for routine work in the user’s own repositories or ongoing monitoring after submission.
Convert raw Markdown tool output into Elastic Cloud Serverless changelog format using GitHub PR context and prior Serverless release notes. Use when drafting or editing Serverless changelog entries from release notes generator output.
application / serviceのenvironment secretをInfisical中心で設計・初期化・移行・検証する時に使用する。CLI-first、repository-controlled schema、Machine Identity、GitHub OIDC、agent least-privilege、secret-safe evidenceを扱う。
Use when setting up or repairing a Roblox team project outside Studio: Rojo or Script Sync, Wally packages, Rokit pins, luau-lsp type checking, Selene, StyLua, unit tests in Lune or the engine, GitHub Actions CI on pull requests, Open Cloud place publishing, Luau Execution or API key scopes, merging builders' Team Create map with code from files, Studio plugins, or proving a pipeline works. Also when users say "set up Rojo", "CI for my Roblox game", "run tests in CI", "publish from GitHub", "Script Sync stopped syncing", "Rojo deleted my parts", "wally packages not found", "luau-lsp can't find ReplicatedStorage", "selene errors on types", "the release wiped the map" or "my LocalScript doesn't run".
Day5 예지보전 실습판(10분) — 설비센서 가상 데이터로 노이즈와 추세를 판정하고 그래프 한 장짜리 대시보드를 GitHub Pages로 공개하는 강의. "/learn-pdm-lite-hgd", "예지보전 실습판", "5일차 노이즈 vs 추세", "Day5 예지보전 10분 실습" 요청에 사용.
Provide a situation report on the current work: objective, done, in progress, blocked, next, and open questions. Default window is everything since the session start or the previous sitrep in this conversation, whichever is later. Evidence comes from session history plus read-only git/GitHub checks. Use when the user says "sitrep", "situation report", "status report", "where are we", "what's happened", "catch me up", or after a long run to summarise state.
Open a draft PR for every unblocked (frontier) ticket of a spec and hand each to GitHub Copilot to implement. Use when the user wants to delegate ready tickets to Copilot, open PRs for unblocked tickets, or have Copilot start implementing a spec's tickets.
Spar with GitHub Copilot's PR reviewer — an unattended agent-to-agent loop that addresses Copilot's comments round after round until it recommends approval, without drifting from the PR's charter. Use when asked to address Copilot's review comments or get Copilot to approve a PR.
Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.
Fix failing CI checks and GitHub Actions on a Pull Request.
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.