cicd
4.9K
code-exec-fallback-266cba
Fallback workflow for reliable code execution when sandbox fails repeatedly
HKUDS
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
cicd
4.9K
finalize-zip-deliverable
Ensures codebase deliverables are properly archived into a ZIP file before marking task complete
HKUDS
devops
cicd
4.9K
search-fallback-workflow
Graceful degradation workflow for continuing tasks when web search tools fail, using internal knowledge with verification caveats
HKUDS
devops
cicd
4.9K
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase
HKUDS
devops
containers
4.9K
panel-retry-localstorage
Enhanced dashboard panel component with robust error handling, retry logic, and localStorage persistence for state management.
HKUDS
devops
git-workflows
4.9K
sandbox-file-discovery-and-validation
Use shell tools safely in sandboxed environments by discovering files from real workspace roots instead of assumed user folders, then explicitly verifying output artifacts after generation.
HKUDS
devops
git-workflows
4.9K
project-scaffold
Scaffold a Vite + TypeScript personal dashboard project with the correct directory structure, dependencies, and configuration files.
HKUDS
devops
git-workflows
4.9K
typescript-compile-check-resilient-fallback
A resilient workflow for running TypeScript compile checks (tsc --noEmit) that falls back gracefully when npx or direct binary invocations fail, and distinguishes pre-existing errors from newly introduced ones.
HKUDS
devops
cicd
4.9K
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
microsoft
devops
git-workflows
4.9K
fluid-pr
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
microsoft
devops
git-workflows
4.9K
fluid-release
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the schedule and repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.
microsoft
devops
git-workflows
4.7K
build-from-issue
Given a GitHub issue number, plan and implement the work described in the issue. Operates iteratively - creates an implementation plan, responds to feedback, and only builds when the 'state:agent-ready' label is applied. Includes tests, documentation updates, and PR creation. Trigger keywords - build from issue, implement issue, work on issue, build issue, start issue.
NVIDIA
devops
git-workflows
4.7K
create-github-issue
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
NVIDIA
devops
git-workflows
4.7K
create-github-pr
Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.
NVIDIA
devops
git-workflows
4.7K
review-github-pr
Review a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary.
NVIDIA
devops
git-workflows
4.7K
review-security-issue
Given a GitHub issue, review the issue for security implications. You'll make a determination if the claim in the issue is legitimate and should be addressed or will be a "won't fix." Trigger keywords - security issue, review security ticket, review security issue.
NVIDIA
devops
git-workflows
4.7K
update-docs-from-commits
Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.
NVIDIA
devops
git-workflows
4.7K
watch-github-actions
Watch and monitor GitHub Actions workflow runs using the gh CLI. Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress. Trigger keywords - watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status.
NVIDIA
devops
containers
4.7K
dual-edition-module-migration
Migrate modules between shared `src/opensource/` code and enterprise overlays under `enterprise/src/opensource/`, while preserving the `src/opensource` boundary and existing component override points.
dtyq
devops
git-workflows
4.5K
issue-triage-report
Generate comprehensive GitHub Feature Area Status reports for the Windows App SDK repository. Use when asked to create triage reports, identify high-priority issues, analyze feature area health, find issues needing attention, or generate status dashboards. Triggers on requests involving issue triage, area status, priority analysis, bug tracking reports, or engineering team focus areas.
microsoft
devops
git-workflows
4.5K
worktree-manager
Create and manage Git worktrees for parallel development workflows. Use when multiple self-contained issues should NOT be fixed in a single branch, when human-Copilot iteration requires isolated environments with separate chat history and commits, or when parallel work items need independent build/test results. Triggers on requests involving branch isolation, work item separation, parallel development, or avoiding messy branch switching.
microsoft
devops