Loading...
Loading...
Found 3,749 Skills
Run /check-onboarding, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-onboarding instead if you want to fix issues immediately.
Create product documentation with help pages, AI-generated screenshots, Remotion product videos with TTS narration and background music, and GitHub README visual documentation. Use when asked to create documentation, a help page, product tour video, generate screenshots, add user guides, or enrich a GitHub README.
Fetch unresolved PR comments (both code-level and PR-level), validate issues, and fix them. Also checks CI status and fixes failing tests, lint errors, and build issues. Use when reviewing and addressing GitHub PR feedback. Filters out resolved comments, keeps only the last claude[bot] comment per thread, validates issues, posts review report as a PR comment, then fixes validated issues.
Git-aware smart revert for tracks, phases, and tasks. Handles rewritten history, finds related commits, and provides safe rollback with multiple confirmation gates.
Skills for accessing and searching docs in DeepWiki/GitHub’s public code repositories can help users understand open-source project source codes, and users can also ask questions directly about the code docs.
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Unblock a PR: resolve conflicts, fix CI, address reviews. Composes: git-mastery conflict resolution, /fix-ci, /respond, /address-review. Use when: PR is blocked by conflicts, red CI, or unaddressed review feedback.
Triages new GitHub issues — classifies, reproduces bugs, attempts conservative fixes, and comments. Use when a new issue is opened and needs automated triage.
Merges valuable content into permanent documentation, then deletes source files. Use when you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews. Do not use when files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value.
Stream-backup active recordings to GitHub. TRIGGERS - backup recording, sync cast, streaming backup.
Publish the openwork-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openwork-orchestrator npm publish" - "publish openwork-orchestrator" - "bump openwork-orchestrator"
Project status report generation from git history, task context, and milestone tracking. Use when creating weekly updates, sprint reviews, stakeholder reports, or project dashboards.