amplifier-opencode-bugfixTriage and fix an amplifier-app-opencode bug, from report to verified fix, using E2E-test-driven development. Covers intake, ruling out non-code causes (stale server, stale install, mismatched floor), root-cause pinning, the coverage-gap gate that classifies…amplifier-opencode-new-featureDevelop a new amplifier-app-opencode feature from ideation to working end-to-end in a DTU, using E2E-test-driven development with the spec landing in the same commit as the contract change. Covers orientation, planning, spec-first review, red/green E2E TDD,…amplifier-opencode-releaseRelease amplifier-app-opencode: bound the commit range, sweep the diff for anything that should not ship, bump both version declarations in agreement, write the changelog, confirm the agent-version floor decision, run the local gate, and open the release PR.…
مستكشف المستودعات
microsoft · المستودعات و skills الممثلة - الصفحة ١٤
عرض على مستوى المستودعات لـ ٢٬٥١٥ skills مجمعة عبر ٣٢١ مستودعات GitHub.
drumbeat-automation-authoringAuthor and validate drumbeat automation files — the closed-vocabulary YAML frontmatter contract. Covers the registered top-level keys, structured `steps:` objects ({id, prompt, label?} — steps live in the frontmatter, never the markdown body), the schedule…drumbeat-operationsInstall, run, supervise, and troubleshoot the drumbeat automation engine and its `drumbeat` CLI. Covers the single `uv tool install`, workspace `init`, the `doctor` staleness check, running under a supervisor (`service install|status| uninstall` — systemd…drumbeat-drumpack-authoringAuthor drumbeat drumpacks — the tool-bundle contract that brings your own tools to the engine. Covers the drumpack directory layout, the `drumpack.md` card and its required frontmatter (`pack_format`, `name`, `description`, `tools`), the loader's fail-loud…
releasePrepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat…agent-lightningProvides the action space, tradeoffs, and evaluation context for improving an editable AI agent against a benchmark while preserving its deployment contract. Use when optimizing agent accuracy, cost, latency, or reliability.
add-garnet-commandAdds a new built-in RESP command to Garnet end-to-end. Covers enum registration, parsing, dispatch, RESP handler, API surface, storage session, RMW callbacks, command metadata JSON, ACL tests, and integration tests. Use when asked to "add a command",…pr-finalizeFinalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation…
release-processGuide for performing the DirectXMath release process. Use this skill when asked to help with releasing a new version, publishing packages, or updating ports.directxmath-usageGuide for integrating DirectXMath into new projects and an overview of the API, types, and classes. Use this skill when asked about how to use DirectXMath, integrate it into a project, or for an overview of available functionality.
formatting-and-lintingFormat and lint CCF changes. Use when choosing or running checks for C++, Python, TypeScript, JavaScript, Markdown, YAML, JSON, CMake, shell scripts, or release notes, and when deciding which checks support automatic fixes.testingRun and write CCF tests. Use when selecting or executing unit, end-to-end, partition, compatibility, coverage, or Python SDK tests, or when adding an e2e test. Covers test labels, the tests.sh wrapper, e2e infrastructure, and test patterns. Never call ctest…
al-code-reviewReview AL code for Dynamics 365 Business Central across specialized domains. Supports domain-specific analysis (security, performance, style, accessibility, upgrade, privacy) with expertise-matched models. Handles Microsoft Dynamics 365 localization…al-docsThis skill should be used when the user asks to "document AL code", "generate docs for this app", "create documentation for this extension", "document this BC app", "set up docs for this AL project", "refresh my docs after code changes", "what documentation…