Loading...
Loading...
Found 236 Skills
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
Implement one GitHub Issue at a time — tests, review, gates, commit. Never mirror tickets to disk.
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix
Activates a work item or issue and creates the feature branch in one step. Supports ADO work items and GitHub issues, selected via the ISSUE_TRACKER config setting. Use when the user says "start story", "start working on", "begin AB#N", "kick off AB#N", "start issue
Interview the requester, then draft and file a complete Elastic documentation issue against the right template and repository — enforcing the good-issues quality bar, checking for duplicates and existing coverage first, rewriting implementation-side detail into user-facing terms, and routing sensitive requests privately. Use it to request docs for a feature, hand off notes or a pull request, request a UI copy review, report a problem with a published page, share support feedback privately, or ask how to request documentation support.
Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory. Given the URL of a GitHub issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase as a native GitHub sub-issue of the parent. Stops for user approval before creating any issue. After creation, the plan is meant to be implemented with the codely-plan-phase-implement-github skill.
Sweep flagged Outlook threads, or threads named by subject, into GitHub issues or comments.
Safe GitHub Issues read/write via gh — labels, related-issue discovery, blockers. Specs stay on GitHub.
Turn a spec into GitHub tickets using Matt Pocock's to-tickets skill, attaching every ticket as a native sub-issue, adding ticket, and defaulting to status/todo when no status/ label exists.
Analyze a GitHub issue and create a detailed technical specification
Track Remotion CI flakes in issue
OPT-IN skill. Send developer-experience feedback about the TomTom Maps SDK for JavaScript (@tomtom-org/maps-sdk) to its public GitHub repository, tomtom-international/maps-sdk-js, as an issue or a discussion. Use at the START of any work with the SDK to ask the developer once for permission (the tomtom-maps-sdk-js skill hands over here for that), and after that whenever the SDK gets in the way while building — the docs, types or AI skill did not say what was needed; the API cannot express what the developer asked for; the code that actually works differs from what the docs or examples showcase; or something is plainly broken. Also use when the developer says "report this", "send feedback", "file an issue", "tell TomTom", "stop sending feedback", or asks what feedback has been collected so far. Drafts a redacted report and posts it only after the developer approves that draft.