* doublecheck: auto-escalate to full report for high-risk content
In active (persistent) mode, doublecheck previously used abbreviated
inline verification for all content types, with the full three-layer
report only available if the user explicitly requested it. Most users
did not know the command existed, so high-stakes content (legal
analysis, regulatory guidance) and responses with DISPUTED or
FABRICATION RISK findings were presented with only a summary table.
Changes:
- Auto-escalate to the full verification report when any claim rates
DISPUTED or FABRICATION RISK during inline verification
- Always use the full report for legal analysis, regulatory
interpretation, compliance guidance, and content with case citations
or statutory references
- Update the activation message to mention the 'full report' command
- Add a discoverability footer to inline verification sections
- Update README.md to document the new behavior
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address review feedback: fix table reference, reconcile bullets, clarify callout placement, add trigger phrase
- Table row now references 'high-stakes content rule' (not 'auto-escalation
rule') and lists all content types that match the later rule text
- README first bullet no longer claims legal content gets inline
verification, resolving the contradiction with the next bullet
- Clarify that the 'Heads up' callout goes at the top of the full report
when auto-escalation applies, not in a nonexistent inline section
- Add 'full report' to the explicit trigger phrase list in the 'Offer
full verification on request' rule
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update README.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update README.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add doublecheck plugin: three-layer verification pipeline for AI output
Adds a new plugin that helps users verify AI-generated content before
acting on it. Designed for sensitive contexts (legal, medical, financial,
compliance) where hallucinations carry real consequences.
Three verification layers:
- Self-Audit: extracts verifiable claims, checks internal consistency
- Source Verification: web searches per claim, produces URLs for human review
- Adversarial Review: assumes errors exist, checks hallucination patterns
Supports persistent mode (auto-verifies every factual response inline)
and one-shot mode (full report on specific text). Confidence ratings:
VERIFIED, PLAUSIBLE, UNVERIFIED, DISPUTED, FABRICATION RISK.
Includes:
- Skill (skills/doublecheck/) with bundled report template
- Agent (agents/doublecheck.agent.md) for interactive verification
- Plugin package (plugins/doublecheck/) bundling both
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address review: fix tools YAML format, remove materialized artifacts
- Fix tools frontmatter in agents/doublecheck.agent.md to use standard
YAML list format instead of flow sequence with trailing comma
- Remove plugins/doublecheck/agents/ and plugins/doublecheck/skills/
from tracking; these paths are in .gitignore as CI-materialized
artifacts that should not be committed
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Autonomous backup agent for GitHub Copilot CLI skills. Watches, syncs,
and pushes skill changes to GitHub in real time. One-line install,
survives reboots, zero interaction after setup.
Co-authored-by: DUBSOpenHub <DUBSOpenHub@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Some layout tweaks
* SSR resource listing pages
Render resource listing pages in Astro for first paint and hydrate client filtering/search behavior on top.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fixing font path
* removing feature plugin reference as we don't track that anymore
* button alignment
* rendering markdown
* Improve skills modal file browsing
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improving the layout of the search/filter section
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add dependency/blocking trigger phrases to skill description so the
skill activates on requests like 'link issues', 'add dependency',
'blocked by', and 'blocking'
- Fix incorrect GraphQL return field in dependencies.md: blockedByIssue
does not exist on AddBlockedByPayload; the correct field is
blockingIssue
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: show external plugins on the website
Read plugins/external.json during website data generation and include
external plugins alongside local ones in plugins.json. External plugins
are flagged with external:true and carry metadata (author, repository,
homepage, license, source).
On the website:
- Plugin cards show a '🔗 External' badge and author attribution
- The 'Repository' button links to the source path within the repo
- The modal shows metadata (author, repo, homepage, license) and a
'View Repository' CTA instead of an items list
- External plugins are searchable and filterable by tags
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: address PR #937 security and UX review comments
- Add sanitizeUrl() function to validate URLs and prevent XSS via javascript:/data: schemes
- Add rel="noopener noreferrer" to all target="_blank" links to prevent reverse-tabnabbing
- Change external plugin path from external/<name> to plugins/<name> for proper deep-linking
- Track actual count of external plugins added (after filtering/deduplication) in build logs
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Assigns ownership of napkin plugin and skill to @dvelton
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add napkin plugin: visual whiteboard collaboration for Copilot CLI
Napkin opens an interactive HTML whiteboard in the user's browser where
they can draw, sketch, and add sticky notes. When ready, they click
'Share with Copilot' which exports a PNG snapshot. The Copilot CLI agent
reads the PNG via the view tool, and the multimodal AI model interprets
the drawings, spatial layout, and text content — responding
conversationally as a collaborator.
Built for non-technical users: lawyers, PMs, business stakeholders,
designers, and anyone who thinks better visually.
Includes:
- Self-contained HTML whiteboard (zero external dependencies)
- Shape recognition (wobbly shapes snap to clean versions)
- Freehand drawing, sticky notes, arrows, text labels
- Auto-save to localStorage
- SKILL.md with agent instructions
- SVG visual guides for step-by-step README documentation
- Plugin manifest for Copilot CLI installation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix review feedback: roundRect compat, cross-platform shortcuts, eraser undo
- Add safeRoundRect() fallback for browsers without CanvasRenderingContext2D.roundRect()
- Update undo/redo button titles to show Ctrl/Cmd instead of Mac-only Cmd
- Fix eraser undo by capturing state before first erase mutation per gesture
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update plugins/napkin/README.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add missing Line (L) and Eraser (E) keyboard shortcuts to README
The in-app shortcuts panel and keyMap handler both support L for Line
and E for Eraser, but the README keyboard shortcuts table was missing
both entries. Adds them to match the actual implementation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Combine docs/ and templates/ into assets/ per agentskills.io spec
Moves skills/napkin/docs/*.svg and skills/napkin/templates/napkin.html
into skills/napkin/assets/ to align with the Agent Skills specification.
Updates all path references in SKILL.md, README.md, and generated docs.
Addresses review feedback from PR #929.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Dan Velton <dvelton@Dans-MacBook-Pro.local>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* feat: add cli-mastery skill — interactive Copilot CLI training
Adds cli-mastery, an interactive training system for the GitHub Copilot CLI.
8 modules covering slash commands, keyboard shortcuts, modes, agents, skills,
MCP, configuration, and advanced techniques. Includes scenario challenges,
a final exam, XP/leveling system, and SQL-based progress tracking.
Source: https://github.com/DUBSOpenHub/copilot-cli-mastery (MIT)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: address review feedback on frontmatter and consistency
- Switch description from folded block scalar (>) to single-quoted string
per AGENTS.md documented format
- Fix Module 7 heading: backtick-wrap @ separately from 'file mentions'
to avoid implying '@ file mentions' is a literal command
- Fix Final Exam Q6: change '@ + filename' to '@filename' with example
to match the @src/auth.ts syntax taught in modules
- Fix Final Exam Q7: add GEMINI.md to match Module 7 precedence list
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: rename curriculum/ to references/ per agentskills.io spec
Addresses review feedback from @aaronpowell on PR #915.
The Agent Skills specification defines references/ as the standard
directory for supplementary documentation that agents read on demand.
- Renamed skills/cli-mastery/curriculum/ → references/
- Updated all path references in SKILL.md
- Updated asset paths in docs/README.skills.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: DUBSOpenHub <DUBSOpenHub@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Initial plan
* feat: add contributors page to website
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
* feat: add footer with contributors link and fix emoji-only display
- Add custom Starlight Footer component with 'Made with ❤️ by our
amazing contributors' linking to /contributors/
- Filter out contribution types without emoji mappings in the
contributor data generation so only emojis (🎭🎁🧭⌨️🧰) are
shown on the contributors page, not text labels like 'code' or 'doc'
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: use all-contributors HTML output for contributors page
- Restyle all-contributors generated table as a responsive card grid
using CSS grid on tbody with card-styled td cells
- Remove old custom JS search/filter UI and contributors.ts script
- Remove generateContributorsData from data pipeline (no longer needed)
- Keep all-contributors markers for bot regeneration
- Include updated contributor data from .all-contributorsrc
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: CSS fixes for contributors page Starlight compatibility
- Override Starlight table width/overflow to prevent clipping
- Force td width: 100% to counteract HTML width="14.28%" attribute
- Set emoji links to display: inline to prevent vertical stacking
- Improve border visibility with lighter gray color
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add automate-this plugin: screen recording to automation scripts
New plugin that analyzes screen recordings of manual processes and
proposes working automation scripts at multiple complexity tiers.
Features:
- Frame extraction via ffmpeg for visual process reconstruction
- Optional audio transcription via Whisper for narrated recordings
- Environment fingerprinting to constrain proposals to installed tools
- Application-specific automation strategies (browser, spreadsheet,
email, terminal, file management, macOS-native)
- Three-tier proposal system (quick win, full script, scheduled automation)
- Dry-run support for safe testing of all proposals
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update skills/automate-this/SKILL.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Address code review feedback on automate-this plugin
- Fix privacy section: clarify that frames/audio are processed locally
but sent to the Copilot model for analysis (not purely local)
- Replace 'which' with 'command -v' for reliable tool detection with
explicit NO_FFMPEG/NO_WHISPER sentinels
- Use per-run secure temp directory (mktemp -d, mode 0700) instead of
fixed /tmp/ paths to prevent other users reading extracted frames
- Add -y flag and -loglevel warning to ffmpeg calls to prevent
overwrite prompts and avoid piping hiding exit codes
- Add whisper-cpp CLI invocation path so users who install only
whisper-cpp get working transcription
- Fix grouped command syntax in environment fingerprint to prevent
false 'not installed' fallthrough
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add advanced search reference with query syntax guide
Covers search qualifiers, boolean logic, date ranges, missing metadata
filters, common patterns, and when to use search vs list_issues.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add issue fields search support to search and issue-fields references
- Add Advanced Search Mode section to search.md covering field: qualifier,
has:field: syntax, REST advanced_search=true, and GraphQL ISSUE_ADVANCED
- Add Searching by Field Values section to issue-fields.md with REST/GraphQL
examples and qualifier reference table
- Note MCP search_issues limitation (no advanced_search support)
- Update SKILL.md capability table to mention issue field filters
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Clarify three search approaches: list_issues vs search_issues vs advanced search
Replace the simple two-column comparison with a capability matrix showing
what each approach supports (field filters, boolean logic, scope, etc.)
and a decision guide for when to use each one.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix issue field search syntax: use dot notation (field.name:value)
The colon notation (field:Name:Value) is silently ignored by the API.
The correct syntax is dot notation (field.priority:P0) which works in
REST (advanced_search=true), GraphQL (ISSUE_ADVANCED), and web UI.
Also supports has:field.name, no:field.name, and date comparisons.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix github-issues skill: correct MCP tools and add gh api workflows
The skill listed 5 MCP tools that don't exist (create_issue, update_issue,
get_issue, add_issue_comment, list_issue_types), causing tool-not-found
errors when agents tried to follow the skill instructions.
Changes:
- Split tools table into MCP (read ops) and CLI/API (write ops)
- Add gh api commands for creating, updating, commenting on issues
- Document that gh issue create doesn't support --type flag
- Add GraphQL query for discovering issue types
- Remove redundant [Bug]/[Feature] title prefixes (use type param instead)
- Update examples to use gh api instead of non-existent MCP tools
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix sub-issues reference: add gh api examples and integer gotcha
The sub_issue_id parameter requires an integer but gh api -f sends strings,
causing 422 errors. Updated all REST examples to use --input with raw JSON.
Also added:
- Recommended two-step workflow (create issue, then link)
- Explicit warning about -f vs --input for integer params
- Proper gh api command syntax instead of raw HTTP notation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address PR review: fix search docs accuracy and broken link
- Fix misleading claim about full boolean logic support (implicit AND only)
- Remove sort:updated from query example (it's an API param, not a qualifier)
- Clarify -linked:pr comment to avoid confusion with authoring status
- Fix relative link in issue-fields.md (sibling file, not nested path)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improve projects reference: scope warning, gh api examples, issue-side queries
From hands-on usage: hit INSUFFICIENT_SCOPES trying to update project
status because token had read:project but not project write scope.
Added:
- OAuth scope requirements table with gh auth refresh workaround
- How to find an issue's project item ID (query from issue side)
- All GraphQL examples now use gh api graphql (copy-paste ready)
- End-to-end example: set issue status to In Progress
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add images-in-issues reference: hosting methods, pitfalls, screenshots
Documents three approaches for embedding images in issue comments
via CLI: Contents API with github.com/raw/ URLs, browser drag-drop
for permanent user-attachments URLs, and gist hosting limitations.
Includes puppeteer screenshot recipe and comparison table.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update README.skills.md with images reference
Run npm run build to regenerate skill listing.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix issue-fields search: add GraphQL bulk query, caveat search syntax
The field.name:value search qualifier is unreliable via API (returns
0 results even when matching issues exist). Added a recommended
GraphQL approach that fetches issues and filters by issueFieldValues
client-side. Documented the correct IssueFieldSingleSelectValue
schema (name, not value). Marked search qualifier syntax as
experimental with a reliability warning.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs(github-issues): improve project discovery guidance
The projectsV2 query param does keyword search, not exact match,
and sorts by recency. For large orgs like github, common words like
'issue' return 400+ results and bury the target project.
Added a priority-ordered discovery strategy:
1. Direct lookup by number (instant)
2. Reverse lookup from a known issue's projectItems (most reliable)
3. GraphQL name search with client-side jq filtering (fallback)
4. MCP tool (small orgs only)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fixing the action link
* Fix sidebar navigation text contrast in light mode
- Use --sl-color-text-invert instead of --sl-color-white for active
sidebar item, fixing near-black text on dark purple background
(contrast ~2.5:1 → ~7.1:1)
- Bump inactive sidebar links to font-weight 500 for better readability
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Make browser tester generic to support for chrome devotols mcp, playwright, agentic browser tools.
- Add Team lead and energetci peronsality to Orchestrator
- Add progress updates between phases/ waves
* Add copilot-spaces skill for loading project-specific context
New skill that teaches agents to use Copilot Spaces MCP tools
(list_copilot_spaces, get_copilot_space) to discover and load
curated project context into conversations. Covers discovery
workflow, loading spaces by owner/name, and using space content
to ground responses in team-specific docs, code, and standards.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improve copilot-spaces skill with real-world usage patterns
- Add 'Spaces as workflow engines' pattern for multi-step processes
- Add 'Follow the breadcrumbs' step for fetching referenced resources
- Document read-only API limitation (no create/update/delete)
- Add filtering tip for list_copilot_spaces by owner
- Add large output handling guidance (20KB+ spaces)
- Add Example 4: Space as a workflow engine
- Strengthen tips with actionable guidance
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add Spaces CRUD REST API to copilot-spaces skill
- Document full CRUD API endpoints (create, update, delete, collaborators)
- Add 'Managing Spaces' workflow section with gh api examples
- Add Example 5: updating Space instructions programmatically
- Fix incorrect 'read-only' claim - MCP is read-only, REST API is full CRUD
- Add scope requirements (user scope for writes)
- Add resource management tips (array replacement, _destroy)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add instrumentation script for pageview analytics
* Only include analytics tags in production builds
Wrap hydro-marketing analytics meta tag and script in an
import.meta.env.PROD conditional so they are excluded during
local development and only rendered in production builds.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add production-only analytics tags to Starlight Head component
Add hydro-marketing analytics meta tag and script to the custom
Head.astro component override, gated behind import.meta.env.PROD
so they only render in production builds (GitHub Pages deploy).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add issue fields, issue types, and list_issue_types to github-issues skill
- Add list_issue_types to available MCP tools table
- Add type parameter to optional parameters with guidance
- Expand issue types section: MCP tools (preferred) + GraphQL (advanced)
- Document org-level type discovery, create/update with type, GraphQL mutations
- Add issue fields section: discover, read, set via GraphQL
- Note required GraphQL-Features headers (issue_fields, issue_types)
- Update skill description to mention fields, types, dates, priority
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add Projects V2 guidance to github-issues skill
Include MCP tools (projects_list, projects_get, projects_write) and
GraphQL examples for project item management.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add sub-issues section, move issue fields to end with preview note
- Add Sub-Issues and Parent Issues section (MCP, REST, GraphQL)
- Add issue_read tool to MCP tools table
- Move Issue Fields to last section with private preview callout
- Link to community discussion for requesting access
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Prefer issue types over labels for categorization
Update guidance and examples to use type parameter (Bug, Feature)
instead of equivalent labels when issue types are available.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Prefer issue fields over project fields for metadata
Issue fields live on the issue and travel across projects.
Project fields are scoped to a single project.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add issue dependencies (blocked by/blocking) section
Covers REST endpoints (list, add, remove) and GraphQL
(blockedBy, blocking, issueDependenciesSummary, mutations).
Also documents tracked issues read-only fields.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add project discovery workflow for progress reports
Teach agents how to find projects by name, discover fields
and iterations, paginate items, and build status breakdowns.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Generate updated skill listing after SKILL.md changes
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Split skill into reference files per reviewer feedback
Move sub-issues, dependencies, issue types, projects, and issue fields
into separate references/ files. Main SKILL.md now contains core MCP
workflow and a capability table pointing to each reference. This way
the agent only loads the knowledge it needs for the specific task.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add azure-pricing plugin
* changes for azure pricing skill
* Remove plugin files, not part of this PR
* added changes for copilot estimator
* refactor: replace Playwright script with web fetch approach for Copilot Studio estimation
- Remove copilot-studio-estimator.py (Playwright browser automation)
- Update SKILL.md to instruct Copilot to fetch live billing rates from Microsoft docs URLs
- Keep COPILOT-STUDIO-RATES.md as cached fallback reference
- No Python dependencies needed — uses Copilot's built-in web fetch tool
* cleanup: remove estimator URL, mark rates as cached fallback
- Remove microsoft.github.io/copilot-studio-estimator from fetch URLs (React SPA, not fetchable)
- Mark billing rates table as dated cached snapshot with fallback notice
- Keep only Microsoft Learn URLs as live data sources
* fix: correct serviceName examples to match API values
* Update skills/azure-pricing/references/SERVICE-NAMES.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* chore: regenerate README.skills.md after build
* fix: remove URL triggering codespell false positive
* feat: add azure-pricing skill to azure-cloud-development plugin
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add search functionality to Learning Hub index page
Add a client-side search bar that filters articles by title, description,
and tags. Sections with no matching results are hidden automatically.
Uses the existing .search-bar CSS pattern from the cookbook page.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chore: remove deprecated layouts, theme script, and learning-hub config
Phase 5 cleanup of Starlight migration:
- Delete BaseLayout.astro (replaced by StarlightPage)
- Delete ArticleLayout.astro (replaced by Starlight docs rendering)
- Delete theme.ts (Starlight has built-in theme toggle)
- Delete src/config/learning-hub.ts (sidebar order now in astro.config.mjs)
- Replace learning-hub glob collection with Starlight docs collection in content.config.ts
- Keep search.ts (still used by homepage and all resource page scripts)
Build verified: 23 pages, no errors.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Migrate website to Starlight with full-text resource search
- Replace bespoke Astro layouts with Starlight integration
- Homepage and resource pages use StarlightPage wrapper
- Learning Hub articles rendered via Starlight docs collection
- Starlight provides search, theme toggle, sidebar, ToC, a11y
- Add custom Pagefind integration for resource search
- All 614 agents/skills/instructions/hooks/workflows/plugins
indexed as custom records with deep-link URLs
- Type filter pills (horizontal pill toggles) above results
- Search results link directly to resource modals via #file= hash
- Move global.css to src/styles/ for Vite processing
- Scope CSS reset to #main-content to avoid Starlight conflicts
- Full-width page gradient via body:has(#main-content)
- Light/dark theme support with Starlight gray scale inversion
- Delete old layouts (BaseLayout, ArticleLayout), theme.ts, config
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address PR review feedback
- Fix pagefind-resources.ts header comment (pagefind:true not false)
- Remove unused base variable in cookbook/index.astro
- Replace hardcoded /awesome-copilot/ paths with relative links in index.md
- Delete stale public/styles/global.css (source of truth is src/styles/)
- Replace fragile getBasePath() with Astro config base in pagefind integration
- Document pagefind:true reasoning in astro.config.mjs
- Use proper visually-hidden pattern + :focus-visible ring for filter pills
- Remove dead header/nav/theme CSS from global.css (~160 lines)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: Prd/ steer support
- Add supprot for PRD
- Vscode steer/ queue support
- Consistent artifacts
- Improved parallel running; for researchers too
* chore: improve prd update support
* chore: Make reviewer use prd for compaince
* chore: imrpvoe websearch in researcher
* fix(gem-team): revert gem-team plugin version from 1.5.0 to 1.2.0
The marketplace currently only includes plugins that live as local
directories in plugins/. This makes it impossible to list plugins
hosted in external GitHub repos, npm packages, or other git URLs.
Add plugins/external.json as a hand-curated list of external plugin
entries following the Claude Code plugin marketplace spec. The
generate-marketplace script now reads this file and merges external
entries as-is into the generated marketplace.json, sorted by name.
Changes:
- Add plugins/external.json (empty array, ready for entries)
- Update eng/generate-marketplace.mjs to load, merge, and sort
external plugins; warn on duplicate names; log counts
- Document the external plugin workflow in CONTRIBUTING.md and
AGENTS.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Scoped custom token only to create-pull-request safe output.
All other operations use default token fallback chains.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Without explicit github-token, the compiler generates a proper
fallback chain (GH_AW_GITHUB_TOKEN || GITHUB_TOKEN) ensuring
a valid token is always available for git push operations.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
