Add a new skill for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components v4) in Blazor applications. Includes guidance on setup, component usage, theming, data grids, layout and navigation.
- Change invocation to /sponsor owner/repo
- Rename 'Sponsor These' to 'Ways to Give Back'
- Soften language: never shame unfunded projects
- Add rule: always be encouraging, never shaming
- Regenerate READMEs
- Removed re-added collections/ path triggers from CI
- Merged plugin checklist improvements from both branches
- Kept plugin:generate-marketplace script from main
- Removed new ospo-sponsorship collection file (plugin already exists)
- Dropped obsolete plugin:migrate and plugin:refresh scripts
Replace Collections with Plugins as first-class citizens in the repo.
With the Copilot CLI v0.409 release making plugins an on-by-default
marketplace, collections are redundant overhead.
## What changed
### Plugin Infrastructure
- Created eng/validate-plugins.mjs (replaces validate-collections.mjs)
- Created eng/create-plugin.mjs (replaces create-collection.mjs)
- Enhanced all 42 plugin.json files with tags, featured, display, and
items metadata from their corresponding collection.yml files
### Build & Website
- Updated eng/update-readme.mjs to generate plugin docs
- Updated eng/generate-website-data.mjs to emit plugins.json with full
items array for modal rendering
- Renamed website collections page to plugins (/plugins/)
- Fixed plugin modal to use <div> instead of <pre> for proper styling
- Updated README.md featured section from Collections to Plugins
### Documentation & CI
- Updated CONTRIBUTING.md, AGENTS.md, copilot-instructions.md, PR template
- Updated CI workflows to validate plugins instead of collections
- Replaced docs/README.collections.md with docs/README.plugins.md
### Cleanup
- Removed eng/validate-collections.mjs, eng/create-collection.mjs,
eng/collection-to-plugin.mjs
- Removed entire collections/ directory (41 .collection.yml + .md files)
- Removed parseCollectionYaml from yaml-parser.mjs
- Removed COLLECTIONS_DIR from constants.mjs
Closes#711
Major upgrade:
- deps.dev GetDependencies: full tree in one call (direct + transitive)
- deps.dev GetVersion: cross-ecosystem package→repo mapping (7 ecosystems)
- deps.dev GetProject: OSSF Scorecard health data per project
- Direct vs transitive column (✅ vs ⛓️)
- Health column from Scorecard Maintained check
- Actionable minimum: '💡 Sponsoring just N people covers all funded deps'
- Graceful fallback to registry APIs if deps.dev unavailable
Inspired by jshchnz/tribute, adds:
- Link verification: every funding URL is fetched before presenting
- Web search fallback: finds funding even without FUNDING.yml
- How Verified column: transparency about data source
- 5 ecosystems: npm, Python, Rust, Go, Ruby (was npm-only)
- Corporate-maintained package detection
- No Verified Funding Found section for unfunded deps
Teaches Copilot how to scan a repo's dependencies and find which ones
accept sponsorship via GitHub Sponsors, Open Collective, etc.
Workflow:
1. Fetch package.json from target repo
2. Resolve each dep to source GitHub repo via npm registry
3. Check npm funding field + .github/FUNDING.yml
4. Group by maintainer, present report with sponsor links
Tested against expressjs/express: found 9/28 deps sponsorable (32%)
across 3 funding destinations.
Create new prompt that suggests relevant GitHub Copilot skills from the
awesome-copilot repository based on repository context and chat history,
following the same pattern as existing suggest prompts for agents,
instructions, prompts, and collections.
Co-authored-by: NoahJenkins <41129202+NoahJenkins@users.noreply.github.com>
Adds a Copilot CLI skill that teaches absolute beginners how to use
GitHub Copilot CLI through guided, interactive lessons right in the
terminal. Features:
- Dual-track learning: Developer (8 lessons) and Non-Developer (7 lessons)
- Interactive exercises using ask_user
- SQL-based progress tracking
- On-demand Q&A with live doc fetching
- Beginner-friendly with CLI glossary and fallback handling
Source repo: https://github.com/DUBSOpenHub/copilot-cli-quickstart
- Introduced new agents: gem-chrome-tester, gem-devops, gem-documentation-writer, gem-implementer, gem-orchestrator, gem-planner, gem-researcher, and gem-reviewer.
- Updated README.collections.md to include the new Gem Team Multi-Agent Orchestration collection.
- Created gem-team.collection.yml and gem-team.md for structured documentation of the multi-agent orchestration framework.
- Each agent includes detailed descriptions, workflows, operating rules, and final anchors for clarity on their functionalities and usage.
Add an agent for AI-powered LinkedIn content creation, scheduling, and
analytics through Reepl (https://reepl.io). Enables creating posts,
carousels, and managing LinkedIn presence directly from GitHub Copilot.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add tools for maximizing GitHub Copilot effectiveness through better
context management:
- Instructions: Guidelines for structuring code so Copilot understands it
- Agent: Context Architect - plans multi-file changes by mapping dependencies
- Prompts:
- context-map: Map all affected files before changes
- what-context-needed: Ask Copilot what files it needs
- refactor-plan: Create phased refactor plans with rollback steps
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Introduced hooks to enable automated workflows triggered by specific events during GitHub Copilot sessions.
- Added documentation for hooks in AGENTS.md and README.md.
- Created a new directory structure for hooks, including README.md and hooks.json files.
- Implemented two example hooks: Session Auto-Commit and Session Logger.
- Developed scripts for logging session events and auto-committing changes.
- Enhanced validation and parsing for hook metadata.
- Updated build and validation scripts to accommodate new hooks functionality.
