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

forge-ai-assist

v1.1.15

Published

Install and run Forge Copilot summonables for GitHub discussion analysis.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ajitgunturiajitgunturi

Keywords

copilotgithub-discussionsai-assistantcliforge

Readme

Forge

Forge installs GitHub discussion-analysis and issue-analysis runtimes under ~/.copilot, ~/.claude, ~/.codex, and ~/.gemini.

Install

npx forge-ai-assist@latest

When run in a terminal, Forge will ask whether to install copilot, claude, codex, gemini, or all. For automation, you can skip the prompt:

npx forge-ai-assist@latest --assistants all
npx forge-ai-assist@latest --assistants copilot
npx forge-ai-assist@latest --assistants claude
npx forge-ai-assist@latest --assistants codex
npx forge-ai-assist@latest --assistants gemini

If npm keeps serving a stale cached release, force an online refresh:

npm_config_prefer_online=true npx forge-ai-assist@latest

Use

In Copilot:

  1. Run /agent
  2. Select forge-discussion-analyzer or forge-issue-analyzer
  3. Ask a question about GitHub Discussions or GitHub Issues

For gh copilot, Forge installs matching skills at:

  • ~/.copilot/skills/forge-discussion-analyzer/SKILL.md
  • ~/.copilot/skills/forge-issue-analyzer/SKILL.md

This keeps delegation pointed at the same Forge command instead of failing with Skill not found.

In Claude Code:

  1. Use the installed forge:discussion-analyzer or forge:issue-analyzer command
  2. The command delegates to the matching installed agent and the runtime bundle under ~/.claude/forge
  3. Ask a question about GitHub Discussions or GitHub Issues

In Codex:

  1. Use $forge-discussion-analyzer or $forge-issue-analyzer from ~/.codex/skills/
  2. Codex also gets a matching agent and agent TOML under ~/.codex/agents/
  3. Ask a question about GitHub Discussions or GitHub Issues

In Gemini:

  1. Use forge:discussion-analyzer or forge:issue-analyzer from ~/.gemini/commands/forge/
  2. Gemini also gets a matching agent under ~/.gemini/agents/
  3. Ask a question about GitHub Discussions or GitHub Issues

Custom Instructions

Forge installs:

  • ~/.copilot/agents/forge-discussion-analyzer.agent.md
  • ~/.copilot/skills/forge-discussion-analyzer/SKILL.md
  • ~/.copilot/agents/forge-issue-analyzer.agent.md
  • ~/.copilot/skills/forge-issue-analyzer/SKILL.md
  • ~/.claude/commands/forge/discussion-analyzer.md
  • ~/.claude/agents/forge-discussion-analyzer.md
  • ~/.claude/commands/forge/issue-analyzer.md
  • ~/.claude/agents/forge-issue-analyzer.md
  • ~/.codex/skills/forge-discussion-analyzer/SKILL.md
  • ~/.codex/agents/forge-discussion-analyzer.md
  • ~/.codex/agents/forge-discussion-analyzer.toml
  • ~/.codex/skills/forge-issue-analyzer/SKILL.md
  • ~/.codex/agents/forge-issue-analyzer.md
  • ~/.codex/agents/forge-issue-analyzer.toml
  • ~/.gemini/commands/forge/discussion-analyzer.toml
  • ~/.gemini/agents/forge-discussion-analyzer.md
  • ~/.gemini/commands/forge/issue-analyzer.toml
  • ~/.gemini/agents/forge-issue-analyzer.md

The markdown assets include a preserved user-customizations block.

  • Add your own Copilot instructions inside the BEGIN USER CUSTOMIZATIONS / END USER CUSTOMIZATIONS section.
  • Add your own Claude instructions inside the same markers in the Claude command or agent files.
  • Add your own Codex instructions inside the same markers in the Codex skill file.
  • Add your own Gemini instructions inside the same markers in the Gemini agent file.
  • Leave the Forge-managed section unchanged.
  • Upgrades replace only the Forge-managed block, so your custom instructions stay intact across reinstalls and updates.

Notes

  • forge-discussion-analyzer works with GitHub Discussions only.
  • forge-issue-analyzer works with GitHub Issues only.
  • Analysis traces are written to the repository .forge directory.
  • Forge installs into ~/.copilot, ~/.claude, ~/.codex, and ~/.gemini. It does not install any files under ~/.config/gh.
  • If Forge hits a network or GitHub API timeout, the installed Copilot agent is expected to report the Forge failure and stop rather than falling back to raw gh api calls.
  • More development and release details are in CONTRIBUTING.md.