mirror of https://github.com/kunchenguid/chrome-devtools-axi.git synced 2026-09-14 16:27:17 +08:00

Files

T

lmn451 a970109ced feat(bridge): add shared MCP server transport modes (#139 )

* feat: connect AXI to a shared MCP server

* no-mistakes(review): Require compatible shared MCP proxies and document same-host usage

* no-mistakes(document): Clarify shared MCP setup and transport documentation

* fix: surface shared MCP startup guidance

* no-mistakes(document): Document shared MCP startup configuration and CLI help

* feat: support direct and proxied shared MCP

* no-mistakes(review): Fix proxy health guidance and remove source-only test

* no-mistakes(document): Updated shared MCP docs; fixed client formatting

2026-09-12 05:22:55 -07:00

3.3 KiB

Raw Permalink Blame History

Contributing

Thanks for wanting to contribute. One rule up front:

Human-authored pull requests targeting main must be raised through no-mistakes. We require this to reduce the maintainer's burden of reviewing and merging contributions.

no-mistakes puts a local git proxy in front of your real remote. Pushing through it runs an AI-driven review/test/build pipeline in an isolated worktree, forwards the push upstream only after every check passes, and opens a clean PR automatically.

A GitHub Actions check (Require no-mistakes) runs on PRs targeting main and fails if the body is missing the deterministic signature that no-mistakes writes. It also requires the machine-readable pipeline attestation that no-mistakes >= 1.46.0 writes next to that signature: the review, test, and document steps must all be recorded as completed, and the attested head_sha must be the PR's current head. The gate runs when a PR is opened, edited, or reopened, not when commits are pushed. If a direct push leaves a stale attestation, head binding rejects it the next time one of those gate events runs; use git push no-mistakes so the body is rewritten for the new head. The release and dependency bots are exempt so their automation keeps working, but regular contributor PRs without the signature and a current attestation will not be reviewed or merged.

Workflow

Fork routing requires no-mistakes v1.30.1 or newer.

Fork the repo, then clone the parent repo or set your local origin back to the parent repo (git@github.com:kunchenguid/chrome-devtools-axi.git).
Create a branch and make your changes.
Initialize or refresh the gate with your fork as the push target: no-mistakes init --fork-url git@github.com:<you>/chrome-devtools-axi.git.
Commit your changes.
Push through the gate instead of pushing to origin:
```
git push no-mistakes
```
Run no-mistakes to attach to the pipeline, watch findings, and auto-fix or review as needed.
Once the pipeline passes, it pushes your branch to your fork and opens the PR against this parent repo for you.

See the no-mistakes quick start for the full first-run walkthrough.

Repo conventions

Node 20+, TypeScript, ESM-only.
See AGENTS.md for test and formatting commands.
Use pnpm for package scripts.
Run pnpm run build and pnpm test before pushing.
The pipeline will run them again, but a fast local pass saves rounds.
Do not hand-edit skills/chrome-devtools-axi/SKILL.md.
It is a minimal discovery stub generated from src/skill.ts by pnpm run build:skill, and pnpm test fails if it drifts.
Update src/skill.ts for body or frontmatter changes; the stub points to the CLI instead of duplicating its guidance.
Keep skills/chrome-devtools-axi/ in the npm package files list so releases include the installable Agent Skill.
Do not hand-edit CHANGELOG.md or .release-please-manifest.json.
They are regenerated by release-please from your conventional commit messages.
Generated files are listed in .prettierignore; validate them with their generator checks instead of formatting them directly.

Questions

Open an issue, or talk to me on Discord.

3.3 KiB Raw Permalink Blame History

Contributing

Workflow

Repo conventions

Questions

3.3 KiB

Raw Permalink Blame History