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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@charlietango/az-pipeline-codex-review-agent

v0.1.0

Published

Codex-based pull request review agent that posts feedback to Azure DevOps

Downloads

7

Readme

Codex Azure Review Agent

CLI that diffs a branch, asks Codex for a structured review, and posts summary + inline suggestion comments back to Azure DevOps.

Usage

pnpm exec codex-azure-review \
  --target-branch refs/heads/main \
  --pr-id 123 \
  --organization https://dev.azure.com/my-org \
  --project MyProject \
  --repository MyRepo

Key flags:

  • --diff-file patch.diff run locally against mocked changes
  • --review-time-budget 20 remind Codex to wrap within ~20 minutes
  • --dry-run only log results; skip Azure comments

Local dry run:

pnpm run review:local

Simulate the Azure Pipelines job locally:

./scripts/run_pipeline_local.sh

Azure Pipelines YAML (azure-pipelines.yml) runs the same steps on an agent. Set secrets OPENAI_API_KEY and AZURE_DEVOPS_PAT, and optionally REVIEW_TIME_BUDGET.

Azure Pipelines template

Copy this minimal pipeline into your project to invoke the included template:

extends:
  template: templates/codex-review.yml
  parameters:
    reviewTimeBudget: '20'
    packageVersion: 'latest'
    dryRun: false

# grant the System.AccessToken to scripts for Azure DevOps REST access
# in the pipeline UI: Settings → "Allow scripts to access the OAuth token"

Secrets OPENAI_API_KEY and AZURE_DEVOPS_PAT must be defined in the pipeline. Set dryRun: true if you want logs only without posting review comments.

Codex contract

Codex returns JSON matching this schema (enforced with Zod):

{
  "summary": "...",
  "findings": [{
    "severity": "major",
    "file": "src/file.ts",
    "line": 12,
    "title": "Issue title",
    "details": "Explanation",
    "suggestion": {
      "file": "src/file.ts",
      "start_line": 10,
      "end_line": 14,
      "comment": "Context",
      "replacement": "New code"
    }
  }],
  "suggestions": [{
    "file": "src/file.ts",
    "start_line": 20,
    "end_line": 22,
    "comment": "Context",
    "replacement": "New code"
  }]
}

Each finding suggestion (and top-level suggestion) becomes a PR comment with a suggestion block, so fixes can be applied inline.

Notes

  • Requires OPENAI_API_KEY (for Codex) and an Azure DevOps PAT (AZURE_DEVOPS_PAT or SYSTEM_ACCESSTOKEN).
  • Runs as ESM (moduleResolution: NodeNext); use pnpm exec tsx locally.
  • Biome + husky/lint-staged keep formatting/linting consistent.