By hd-ecom
Upstash Context7 MCP server — pulls version-specific library documentation and code examples directly into context
npx claudepluginhub hd-ecom/claude-plugins-marketplace --plugin context7Internal Claude Code plugin marketplace for HD Ecom engineering teams. Provides shared skills and enforces consistent AI-assisted development practices org-wide.
| Plugin | Description |
|---|---|
coding-standards | Enforces .NET/C# naming, file structure, and error handling conventions |
pr-review | Structured PR reviews: security, performance, readability, test coverage |
Run once per machine (or per Claude Code profile):
/plugin marketplace add company-tools
When prompted, confirm the source: github:OWNER/claude-plugins-marketplace
Auto-install: If this repo is listed in a project's
.claude/settings.jsonunderextraKnownMarketplaces, Claude Code will prompt you to add it automatically the first time you trust the folder.
After adding the marketplace:
/plugin install coding-standards@company-tools
/plugin install pr-review@company-tools
Or install both at once from the marketplace browser (/plugin marketplace browse company-tools).
When changes are pushed to this repo, update your local copies:
/plugin marketplace update company-tools
Auto-updates: Claude Code checks for marketplace updates at startup. You may be prompted to update automatically.
Once installed, invoke skills via slash commands in Claude Code:
/coding-standards
/pr-review
Or trigger them by describing what you want — Claude will match the relevant skill from context.
To enforce this marketplace org-wide and restrict users to approved sources, deploy the managed-settings.json snippet at the root of this repo via your enterprise Claude Code configuration.
Replace OWNER with your GitHub org name before deploying. The strictKnownMarketplaces setting prevents users from adding unapproved plugin sources.
plugins/
your-plugin-name/ # kebab-case, no spaces
.claude-plugin/
plugin.json # manifest
skills/
SKILL.md # skill content with frontmatter
.claude-plugin/plugin.json
{
"name": "your-plugin-name",
"displayName": "Human Readable Name",
"description": "One sentence: what does this skill help with?",
"version": "1.0.0",
"author": {
"name": "Your Name",
"email": "you@hdecom.com"
}
}
skills/SKILL.md — frontmatter is required:
---
name: your-plugin-name
description: One sentence shown in skill picker and marketplace browser
---
# Skill Title
(Skill content here)
api-testing, not apiTesting or api_testing)${CLAUDE_PLUGIN_ROOT} in hooks or MCP configs if you need to reference plugin-relative pathsplugins/.claude-plugin/marketplace.json:{
"name": "your-plugin-name",
"description": "One sentence description",
"category": "development",
"source": "./plugins/your-plugin-name"
}
./validate-marketplace.sh to check everything is correctclaude-plugins-marketplace/
├── .claude-plugin/
│ └── marketplace.json # Marketplace root manifest
├── plugins/
│ ├── coding-standards/
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json
│ │ └── skills/
│ │ └── SKILL.md
│ └── pr-review/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ └── skills/
│ └── SKILL.md
├── validate-marketplace.sh # Validation helper
└── README.md
Alongside the marketplace repo (in the tooling workspace):
.claude/
settings.json # Project-level: auto-prompts marketplace install
managed-settings.json # Enterprise: org-wide enforcement snippet
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Share bugs, ideas, or general feedback.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Use this agent when you need to fetch and utilize documentation from Context7 for specific libraries or frameworks. Examples: <example>Context: User is building a React application and needs documentation about hooks. user: 'I need to implement useState and useEffect in my React component' assistant: 'I'll use the context7-docs-fetcher agent to get the latest React documentation about hooks' <commentary>Since the user needs specific React documentation, use the context7-docs-fetcher agent to fetch relevant docs and provide accurate guidance.</commentary></example> <example>Context: User is working with Express.js and MongoDB and needs setup guidance. user: 'How do I create a REST API with Express and connect to MongoDB?' assistant: 'Let me use the context7-docs-fetcher agent to get the current documentation for both Express.js and MongoDB' <commentary>The user needs documentation for multiple libraries, so use the context7-docs-fetcher agent to fetch comprehensive docs.</commentary></example>
GitLab DevOps platform integration. Manage repositories, merge requests, CI/CD pipelines, issues, and wikis. Full access to GitLab's comprehensive DevOps lifecycle tools.
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.