菜单
Find similar implementations and prior art for a code pattern across internal repositories — use when checking whether something already exists internally before building it, or looking for reference implementations to follow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Search the public Glean developer documentation for API, SDK, MCP, authentication, indexing, and integration details. Use when the user is building with Glean rather than searching internal company knowledge — trigger phrases include Glean API, Glean SDK, integrate with Glean, indexing API, Glean Python or JavaScript SDK, and how to authenticate with Glean. Don't use it for internal company knowledge, which the using-glean skill covers.
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a defined time window. Trigger phrases include "what did I miss", "catch me up", "I was out", "I'm back from PTO", "summarize while I was away", "what happened last week while I was off", "I just got back", "fill me in on what I missed".
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
Gather architectural context about an internal system from code and documentation across the organization — use when asked to understand a system's architecture, find its repos, or get an overview before working on it.
Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection.
Find usage examples of an API, library, or code pattern across internal repositories — use when looking for how other teams use an internal API, library, or pattern before implementing something new.
| name | similar-code |
| description | Find similar implementations and prior art for a code pattern across internal repositories — use when checking whether something already exists internally before building it, or looking for reference implementations to follow. |
Search for similar implementations across the organization to find prior art, alternative approaches, or shared solutions.
Determine the pattern or feature from the user's request. If not specified, ask before proceeding.
Look for the pattern/feature across all repos:
code_search "[topic] implementation"
code_search "[topic] handler OR service"
code_search "[topic] util OR helper"
The same concept might be named differently:
code_search "[synonym] implementation"
code_search "[synonym] service"
For example, "rate limiting" might also be called "throttling", "quota", "backpressure".
Look for centralized implementations:
code_search "[topic] package OR library"
search "[topic] shared library OR common"
Search for design discussions about this pattern:
search "[topic] design doc OR RFC"
search "[topic] best practices OR guidelines"
For each implementation found, evaluate:
| Test | ✅ Recommended | ⚠️ Acceptable | ❌ Reject |
|---|---|---|---|
| Quality | Clean, tested, well-maintained, follows best practices | Works but has caveats | Hacky, untested, deprecated |
| Maintenance | Commits in past 3 months | Last commit 3-12 months ago | No activity in 12+ months |
| Adoption | Deployed, actively used | Small usage, may have issues | Experiments, abandoned PRs |
| Ownership | Clear maintainer, responds to issues | Works but no clear owner | Orphaned, no maintenance |
Anti-Pattern Signals — reject or warn:
/deprecated/, /old/, /legacy/ paths# Similar Implementations: [Pattern]
## Vetting Summary
| Found | Recommended | Acceptable | Rejected |
|-------|-------------|------------|----------|
| [X] | [Y] | [Z] | [W] |
## Recommended Solution
- **Library**: [name] ([link])
- **Maintained by**: [team/person]
- **Status**: Active, [X] commits in past month
- **Recommendation**: ⭐ Use this instead of building your own
## Vetted Implementations
### ⭐ [Repo Name] — RECOMMENDED
**Quality**: High
**Location:** [path] ([link])
**Last Updated**: [date]
**Maintainer**: [person/team]
**Approach:** [brief description]
**Why recommended:**
- [specific positive pattern]
### [Repo Name] — ACCEPTABLE
**Quality**: Good with caveats
**Location:** [path] ([link])
**Last Updated**: [date]
**Pros:** [advantage]
**Cons:** [limitation]
## Rejected Implementations
| Repo | Reason |
|------|--------|
| [repo] | No commits in 18 months, likely outdated |
| [repo] | Prototype code, never production-ready |
## Pattern Analysis
| Pattern | Used By | Quality | Recommendation |
|---------|---------|---------|----------------|
| [Pattern A] | [X] repos | Good | Follow this approach |
| [Pattern B] | [Y] repos | Mixed | Avoid unless [condition] |
## Recommendations
1. **Best option**: Use [recommended implementation] because [reason]
2. **If that doesn't fit**: Consider [alternative] for [use case]
3. **Avoid**: Don't follow [anti-pattern] approach
# Similar Implementations: [Pattern]
## No Recommended Implementations Found
The assistant searched for implementations of [pattern] but didn't find any worth recommending.
**What was found:** [X] matches, but all were [outdated/low quality/abandoned]
**Suggested next steps:**
1. Check for external libraries: [suggestions]
2. Ask in [relevant Slack channel] about approaches
3. If building new, consider making it a shared library