Loading...
Loading...
Found 236 Skills
Pulls a fitness report from a GitHub issue or from a local fitness report, addresses the action items by updating the codebase, and closes the issue when done. Use when the user says "apply review", "fix review issues", "address review feedback", "apply fitness report", "work through the action items", or provides a GitHub issue URL or number containing a fitness report, even if they don't say "fitness". Not for producing a new report (that's review-full).
Publish one GitHub Issue spec via issue-tracker — chat draft only, no local mirrors.
Use when the user wants several open issues built by agents and turned into pull requests — "work through the issues", "implement the open issues", "clear the backlog", "open PRs for #12 and #15" — optionally at an effort level ("/implement-issues low", "at medium effort"), and when plan pull requests it opened are approved or have comments to answer. Works in Claude Code, Codex, or any agent that can dispatch subagents. Not for one issue the user is building themselves in this session.
Analyze an already-collected infrahub-collect diagnostic bundle — traceback and failure triage across service logs, incident correlation, and known-issue matching against opsmill/infrahub GitHub issues. TRIGGER when: the user says they collected a diagnostic bundle, gives you a bundle path, or pastes bundle contents — and asks what's wrong, wants the logs or tracebacks analyzed, asks "what does this bundle say", wants errors triaged/correlated, or asks whether a crash is a known issue. DO NOT TRIGGER when: no bundle exists yet — collect one first (use infrahub-collecting-diagnostics), filing the issue itself (use infrahub-reporting-issues), or querying live data (use infrahub-analyzing-data).
Turns friction from an Infrahub skill session into a reviewed GitHub issue about an Infrahub skill's guidance. Infrahub skills fail quietly: a missing or unclear rule does not crash, it produces extra round trips and repeated user nudges. This skill gathers evidence of that friction, checks the tracker for an existing report, works out whether the skill or the underlying product is at fault, and drafts a proposed rule change. It never files anything itself: it hands the redacted draft to infrahub-reporting-issues, which shows it to the user and gets explicit approval before any submission. TRIGGER when: accepting a friction offer, the user says "report skill friction", asks why an Infrahub skill kept failing or needed so many retries, or wants a gap in an Infrahub skill's guidance reported. DO NOT TRIGGER when: reporting a bug in Infrahub itself or any other opsmill/infrahub-* product (use infrahub-reporting-issues instead), or for ordinary Infrahub work where nothing went wrong.
Load all open issues from GitHub and save them as markdown files
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.