- Start with the engineering context index and use the context registry to select only relevant topic guides and source files. Recheck implementation at the commit being changed. - Preserve platform, authorization/audit, signing, and lifecycle contracts. Treat design plans as proposals unless linked implementation confirms them. - Follow coding guidance and testing requirements; full build and VM test commands can install tools, modify services, or create cloud resources. - For change assessment, use the review checklist. Separate verified results from…
The Empty Repos Workflow is a GitHub Actions workflow that scans organizations for empty repositories and README-only repositories, generating monthly reports as GitHub issues. Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.
815mo agoReviewMountCreate a free account to mount
AIBAST Agents Library is the stable Microsoft downstream for the RAPP stack (see CONSTITUTION.md for architectural principles): The repository also owns agents/@aibast-agents-library/, registry.json, build_registry.py, rapp_ai/, the production guide, and Microsoft governance files. These are not upstream Grail mirrors. Read beta/GOLDEN_PATH.md before changing the beta. The beta is a chat-driven educational tool: users learn AI by watching GitHub Copilot build, hotload, run, test, explain, screenshot, and record real RAPP capabilities. External AIs can visibly drive the same Brainstem or Brain Surgeon…
This project uses the Spec-Kit agentic development process. Every change MUST follow these rules. Violations will be caught by CI and rejected. This repo uses spec-kit for structured feature development: When assigned an issue: When implementing a task autonomously: 1. Find the relevant spec — Check specs/ for the feature spec matching your issue. Read spec.md, plan.md, tasks.md, and data-model.md before coding. 2. Read the constitution — specs/constitution.md (v1.7.0) defines 15 mandatory architectural principles. Key constraints: - I. API-First: All…
This is a food delivery application with a React TypeScript frontend and .NET backend. Its source is retained for Azure SRE Agent investigation and remediation exercises. Source changes end at a reviewed pull request. Do not add deployment automation, Bicep/AZD infrastructure, registry credentials, or out-of-band Azure Container App updates. Prioritize user experience, maintain clean code architecture, and ensure proper error handling throughout the application.
These instructions apply to any AI agent (Copilot CLI, Copilot Chat, Claude, Cursor, etc.) contributing to this repository. Start from AGENTS.md for the full router of context, conventions, and the build/test loop. - This is a TypeScript GitHub Action (src/index.ts → bundled to dist/ via ncc). - Code style, structure, and test patterns: docs/conventions.md. - GitHub Actions conventions (action.yml, inputs/outputs, secrets, workflow security): docs/github-actions.md. - Test framework and @actions/* mocking pattern: docs/testing-patterns.md. - Build/test loop: npm run build, npm run…
- Treat package.json as the single source of truth for the Tandem release version. - Before publishing or deploying a release, bump the package version with npm version patch --no-git-tag-version or the intended minor/major increment. - Run npm run pack after the bump so the displayed version, generated extension, and ZIP artifact all identify the same release. - Deploy both .github/extensions/tandem/extension.mjs and skills/tandem/SKILL.md to the matching user-scoped installation. The user-scoped provider owns processing when both scopes are loaded. - Edit…
Examples: - @service-approval ./Hackathon --service=bedrock-agentcore-control - @service-approval --service=s3 --framework=ccmv4 Flags can also be expressed in natural language: - "run service approval for bedrock agentcore" - "generate controls for s3 against CCMv4" The pipeline can also run without any MCP servers — pass --no-mcp and facts are verified over the web instead. See the "Running without MCP" section of docs/USAGE-COPILOT.md. The Stop hook runs validate_pipeline_integrity.py and blocks on any rule above.
Infrastructure-as-code that automates deployment of the infrastructure required to run SAP Edge Integration Cell (EIC) on Azure Kubernetes Service (AKS), plus SAP BTP entitlement setup. There is no application code here — only IaC templates and Markdown docs. The repo is split into two maturity tiers, each containing parallel target environments: The production-ready direction is to build on the Azure Well-Architected Framework. All WAF/AKS-baseline scripting lives in the upstream baseline repositories and must only be linked from here, never copied,…
This VS Code extension manages AI assistant catalog resources (chat modes, instructions, prompts, tasks, MCP servers) across multiple repositories. It provides centralized discovery, activation, and "Hats" (preset) functionality for AI resources that enhance GitHub Copilot workflows.
714mo agoReviewMountCreate a free account to mount
This repository maintains the Agentic Co-build plugin, dependency inventory, and documentation site. Customer application code and architecture artifacts belong in the customer's selected repository. The three bundled skill bodies live under plugins/agentic-cobuild/skills/. Select third-party dependencies in scripts/agentic-skills.json; install them from their upstream sources instead of copying them into this plugin. Preserve the creator's discovery confirmation, architecture approval, diagram review gates, and separately initiated implementation handoff. Before changing decision-bearing Microsoft product guidance or Azure SDK code, consult current Microsoft Learn evidence…
This is a multi-sample repository. Each sample folder at the repo root is a completely independent project with its own language, dependencies, configuration, and deployment target.
This sample is part of the microsoft/iq-samples repo. Only read and modify files within this folder (refund-agent-a365/). Do not touch other samples or root-level governance files (LICENSE, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md). This is a Python agent that wraps an Microsoft Foundry agent (with Fabric Data Agent + Work IQ tools) and publishes it to Microsoft Teams / M365 Copilot via the Microsoft Agent 365 (A365) SDK. The Foundry agent handles all intelligence; this project is the A365 hosting wrapper that adds…
This sample is part of the microsoft/iq-samples repo. Only read and modify files within this folder (travel-agent-hosted/). Do not touch other samples or root-level governance files (LICENSE, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md). This is a hosted Microsoft Foundry agent built with the Microsoft Agent Framework SDK. It is a corporate travel assistant grounded with two IQ tools: The agent's intelligence lives in the system prompt in agent/agent.py. The tool wiring (knowledge base + Work IQ Mail) is declared in agent/agent.manifest.yaml and injected…
Azure Monitor OpenTelemetry Profiler for .NET — an SDK that captures performance traces from live .NET applications and uploads them to Application Insights. Ships as the Azure.Monitor.OpenTelemetry.Profiler NuGet package. The repo has three layers plus a submodule: There is also a classic EventPipe profiler under src/ServiceProfiler.EventPipe/ that produces the Microsoft.ApplicationInsights.Profiler.AspNetCore NuGet package. The classic and OTel profilers share code via Microsoft.ApplicationInsights.Profiler.Shared. Build the OTel profiler solution (requires PowerShell 7): This restores, builds, publishes the Uploader, and creates the Uploader.zip that…
This is a Serilog sink that ships structured logs to Azure Data Explorer (Kusto). It is a NuGet library owned by Microsoft. This project uses Central Package Management. All package versions are in src/Directory.Packages.props. Individual .csproj files reference packages without versions. Key rules: - Never add Version= to PackageReference elements in .csproj files — that causes error NU1008 - All version changes go to src/Directory.Packages.props - Some packages have TFM-conditional versions (e.g., System.Text.Json is 8.0.0 for net6.0 and 9.0.0 for…