Integrate Authenticator submodule into skills ecosystem#424
Draft
Integrate Authenticator submodule into skills ecosystem#424
Conversation
Add Authenticator (Microsoft Authenticator app) across all skills, agents, and prompt files to enable agentic work item completion for Authenticator code changes. Changes: - copilot-instructions.md: Add Authenticator to repo organization, repo- specific guidelines with full module catalog, and repository routing table - codebase-researcher: Add Authenticator to repo structure table, key classes section, search scope, and anti-patterns - feature-planner: Add authenticator to repo routing table with routing heuristic, and new Authenticator Feature common pattern - design-author: Include Authenticator in components and cross-repo impact - incident-investigator: Add Authenticator App Issues pattern with module reference for MFA, passkey, NGC, and crypto troubleshooting - pbi-dispatcher: Add authenticator repo routing entry - release-helper: Add note about Authenticator's separate release cycle - test-planner: Add Authenticator-specific test scenario categories - copilot-review-analyst: Add authenticator repo to analysis scope - threat-modeler: Add Authenticator to process components - pbi-template: Add authenticator as valid module target - Agent files: Update codebase-researcher and feature-orchestrator agents with Authenticator search scope and repo slug mapping - Prompt files: Update feature-status and feature-pr-iterate with Authenticator repo slug mapping
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
cacosta33
reviewed
Apr 29, 2026
| * **Common:** This repo holds shared utilities, helper functions, and **all IPC logic**. MSAL/OneAuth use this layer to communicate with Broker. Suggestions in this context should aim for reusability and generality. | ||
| * **ADAL (Azure Active Directory Authentication Library):** Similar to MSAL, this is an authentication library, potentially an older version or specific to certain flows. When working in ADAL context, align with its patterns. | ||
| * **OneAuth:** Third-party library owned by another team (not us). Consumed by 1P Microsoft apps like Teams, Outlook, etc. OneAuth flows start by calling `BrokerMsalController` class methods. | ||
| * **Authenticator (Microsoft Authenticator):** The Authenticator repo contains the Microsoft Authenticator Android application. It is a multi-module Gradle project rooted at `authenticator/PhoneFactor/`. Authenticator consumes SDK library releases from MSAL, Common, and Broker as dependencies. Key modules include: |
Contributor
There was a problem hiding this comment.
Authenticator's Repo has skills that have been tuned for that repo. For example, Authenticator can take advantage of skills that utilize BlueBird's MCP which significantly improves search and results. I believe we can take advantage of that if we perform the following:
Creating a
.vscode/settings.json
and inputting:
// .vscode/settings.json
{
"chat.agentSkillsLocations": [
".github/skills",
"authenticator/.github/skills",
]
}VS Code supports chat.agentSkillsLocations as a setting for additional project skill directories, including multiple skill directories. Reference
We'll probably have to put somewhere in the instructions to only invoke the authenticator skills when authenticator is referenced so as to avoid possible skill clashing
Contributor
There was a problem hiding this comment.
I think that's specific to the codebase-researcher (aspect of FO)?
…ng rules - Create .vscode/settings.json with chat.agentSkillsLocations pointing to both .github/skills and authenticator/.github/skills - Add !.vscode/settings.json to .gitignore so settings are tracked - Add Section 12.1 to copilot-instructions.md documenting Authenticator-specific skills (android-feature-development, android-ui-development, codebase-researcher, incident-investigator, pr-reviewer, prompt-refiner, skill-creator) - Add skill scoping rules to resolve 4 name clashes (codebase-researcher, incident-investigator, prompt-refiner, skill-creator): prefer Authenticator variant for authenticator/ code, android-complete variant for SDK/cross-repo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Authenticator (Microsoft Authenticator app) across all skills, agents, and prompt files to enable agentic work item completion for Authenticator code changes.
Changes: