npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

heyteam-cli

v1.0.4

Published

CLI for setting up HeyTeam AI agents

Readme

HeyTeam Arch 2.0

A zero-dependency architecture for managing deployments using GitHub MCP Server and Slack Webhooks.

🎯 Philosophy

No custom CLI code. No npm packages. Just:

  • AI Agent (GitHub Copilot / Antigravity) as the orchestrator
  • GitHub MCP Server for all GitHub operations
  • Slack Webhook + curl for notifications
  • Markdown files for configuration and prompts.

📋 Configured Repositories

| Repository | Type | Team | |------------|------|------| | digicert/dtm | UI (Frontend) | priti-kumari-dc, surbhi-gupta-dc | | digicert/dtm-backend | Backend | jaydeep-raval-dc, swaraj-dhumale-dc, sharmajetesh |


📁 Structure

Arch2.0/
├── heyteam-instructions.md               # All project config & instructions
├── .github/
│   └── prompts/                          # GitHub Copilot prompt files
│       ├── ship-code.prompt.md           # Commit & push only
│       ├── ship-dev.prompt.md            # Dev deployment
│       ├── ship-int.prompt.md            # Integration deployment
│       ├── ship-release.prompt.md        # Release branch deployment
│       └── ship-prod.prompt.md           # Production deployment
└── .agent/
    └── workflows/                        # Antigravity workflow files
        ├── ship-code.md
        ├── ship-dev.md
        ├── ship-int.md
        ├── ship-release.md
        └── ship-prod.md

🏷️ Labels by Environment

| Command | Backend Label | UI Label | Slack | |---------|---------------|----------|-------| | ship-code | None (no PR) | None (no PR) | No | | ship-dev | dev-deploy | dev-deploy-user-interface | Optional (default OFF) | | ship-int | integration-deploy | integration-deploy-user-interface | Mandatory | | ship-release | integration-deploy | integration-deploy-user-interface | Mandatory | | ship-prod | prod-deploy | integration-deploy-user-interface | Mandatory |


🌿 Branch Patterns

Deployment Branches

Special branch patterns trigger different target branches:

| Current Branch | Target Branch | |----------------|---------------| | deployment/dev/** | deployment/dev/**-trigger | | deployment/int/** | deployment/int/**-trigger |

Example: deployment/dev/feature-x → PR to deployment/dev/feature-x-trigger

Release Branches

When shipping to "latest release":

  • Search branches matching release/*
  • Use the most recently created one as target

🚀 Usage

With GitHub Copilot

@workspace /ship-code        # Commit & push only (no PR)
@workspace /ship-dev         # Ship to dev (Slack optional)
@workspace /ship-int         # Ship to integration (Slack mandatory)
@workspace /ship-release     # Ship to release branch (Slack mandatory)
@workspace /ship-prod        # Ship to production (Slack mandatory)

With Antigravity

/ship-code       # Commit & push only (no PR)
/ship-dev        # Ship to dev (Slack optional)
/ship-int        # Ship to integration (Slack mandatory)
/ship-release    # Ship to release branch (Slack mandatory)
/ship-prod       # Ship to production (Slack mandatory)

🔔 Slack Integration

Slack notifications are:

  • Optional (default OFF) for: ship-code, ship-dev
  • Mandatory for: ship-int, ship-release, ship-prod

When enabled, notifications are sent using:

curl -X POST -H 'Content-type: application/json' \
  --data '{"PR_LINK": "https://github.com/..."}' \
  'https://hooks.slack.com/triggers/ssdasdasd******'

🔄 How It Works

┌─────────────────┐
│   You (User)    │
└────────┬────────┘
         │ "/ship-dev"
         ▼
┌─────────────────┐
│   AI Agent      │ ◄── Reads heyteam-instructions.md
│ (Copilot/etc)   │     Detects repo (dtm vs dtm-backend)
└────────┬────────┘     Applies correct labels & team
         │
    ┌────┴────┐
    ▼         ▼
┌───────┐  ┌──────┐
│GitHub │  │ curl │
│  MCP  │  │      │
└───┬───┘  └──┬───┘
    │         │
    ▼         ▼
┌───────┐  ┌──────┐
│GitHub │  │Slack │
│  API  │  │Webhook│
└───────┘  └──────┘

📝 Quick Reference

| Feature | How It Works | |---------|-------------| | Create PR | create_pull_request MCP tool | | Add Labels | add_issue_labels MCP tool | | Add Assignees | assign_issue MCP tool + team from config | | Request Reviewers | request_pull_request_review MCP tool | | Find Release Branch | list_branches MCP tool with pattern release/* | | Slack Notification | curl to webhook URL |


Arch 2.0 - Simpler. Leaner. AI-Native.