Repository navigation
chore: fully AI-maintained — policy, scheduled checkups, README badges - #74
Conversation
Same posture as developerz-ai/wurk and db-mcp-gateway (owner, 2026-11-14: no human maintenance unless we add new features). - .dz policy: auto-merge every author's PR on green (was bot + Dependabot only); the review requests changes with a mandatory security pass on auth/OAuth/config/jobs/tools; CLAUDE.md's NEVER list as non_goals; only breaking_change escalates. - Schedules enabled: weekly release-due and health, daily security-release, monthly improve (toolchain bumps included, which Dependabot cannot do). Briefs in .dz/briefs/. - reviewer.md: the three TODO(setup) sections filled from CLAUDE.md. - Dependabot: docker and github-actions monthly, cargo weekly, 14-day cooldown unchanged. - README: badges, star-history chart and an AI-maintained section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🟡 Reviewed6 actionable comment(s) · 5 suppressed (anti-noise) · grounded on your code 🤖 developerz.ai — automated review, running on your model and your box. |
There was a problem hiding this comment.
Review summary — 11 file(s), 6 finding(s).
Critical 0 · Major 0 · Minor 5 · Nit 1
Makes mcp-ssh fully AI-maintained: auto-merge for any author's PR, four scheduled checkups with their briefs, the filled-in reviewer layer, monthly Dependabot for Docker and Actions, and README badges. Two minor README problems: one contradicts the policy and one will go stale.
| File | Findings |
|---|---|
.dz/maintainer/maintainer.yml |
3 minor, 1 nit |
README.md |
2 minor |
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this?
| # Every author's PR is reviewed, babysat and merged on green, except what `escalate` holds for a | ||
| # human and what `non_goals` declines. Whether an author is outside is the platform's read of | ||
| # their real repo permission, never `author_association`. | ||
| auto_merge_scope: any |
There was a problem hiding this comment.
minor · security With auto_merge_scope: any, an outside PR that edits .github/workflows, Dockerfile, deploy/ or .dz/ can auto-merge on green and ship a backdoored image or rewrite this policy. Only the non-goal text at line 45 holds it back, and that depends on an LLM classifying the PR correctly.
| auto_merge_scope: any | |
| auto_merge_scope: any | |
| human_merge: | |
| - ".github/**" | |
| - "bin/**" | |
| - "deploy/**" | |
| - "Dockerfile" | |
| - ".dz/**" |
| - path: "src/oauth/**" | ||
| instructions: *security_review |
There was a problem hiding this comment.
minor · maintainability The security-pass globs match src/auth.rs but not src/auth/revalidate.rs (the stream token re-check) or src/sentry.rs (the credential scrubber), so a PR weakening either gets only the generic src/** instruction. Add src/auth/** and src/sentry.rs entries that use *security_review.
| - path: "src/oauth/**" | |
| instructions: *security_review | |
| - path: "src/auth/**" | |
| instructions: *security_review | |
| - path: "src/sentry.rs" | |
| instructions: *security_review | |
| - path: "src/oauth/**" | |
| instructions: *security_review |
| # `breaking_change`: a human decides a change to the tool surface, CLI, config, auth flow or DB | ||
| # schema that a running install must react to. Security, license and CLA are the platform's | ||
| # hardcoded asks, which this list cannot remove. | ||
| ask_before_acting: [breaking_change] |
There was a problem hiding this comment.
minor · docs ask_before_acting holds only breaking_change and auto_merge_scope: any merges every author, so an outsider's feature PR to this root-shell tool merges on green with no human. That contradicts README.md:169 ("a breaking change or a new feature | a human decides") and the owner's "unless we add new features".
| [](https://github.com/developerz-ai/mcp-ssh/actions/workflows/ci.yml) | ||
| [](https://github.com/developerz-ai/mcp-ssh/releases/latest) | ||
| [](https://github.com/developerz-ai/mcp-ssh/pkgs/container/mcp-ssh) | ||
| [](https://www.rust-lang.org) |
There was a problem hiding this comment.
minor · docs The Rust badge hardcodes 1.100, but the toolchain steps in .dz/briefs/improve.md:25 and .dz/briefs/health.md:24 bump only the three pins, so the badge goes stale on the first automated toolchain bump. Add the README badge to both briefs' toolchain lists, or drop the version from the badge.
| [](https://www.rust-lang.org) | |
| [](https://www.rust-lang.org) |
| | Dependabot | driven to green and merged; every bump waits 14 days after upstream publishes it (security updates excepted) | | ||
| | an outside change to CI, release or publish automation | declined: members maintain the pipeline that publishes the image and the `.deb` | | ||
| | a change that breaks a NEVER rule (secrets in output, root, no TLS, a fourth tool…) | declined with the rule quoted | | ||
| | a breaking change or a new feature | a human decides | |
There was a problem hiding this comment.
minor · docs The README says a new feature goes to a human, but maintainer.yml sets auto_merge_scope: any and lists only breaking_change in ask_before_acting, and its header (lines 7-9) says a human is asked only for breaking changes. So a non-breaking feature PR auto-merges on green, and a contributor relying on this row will be surprised.
| | a breaking change or a new feature | a human decides | | |
| | a breaking change | a human decides | |
| # hardcoded asks, which this list cannot remove. | ||
| ask_before_acting: [breaking_change] | ||
|
|
||
| # The checkups nothing else triggers. One weekday per repo, so the fleet is not hit at once. |
There was a problem hiding this comment.
nit · docs The comment says "One weekday per repo", but security-release runs six days a week (line 151), so the claim is false.
| # The checkups nothing else triggers. One weekday per repo, so the fleet is not hit at once. | |
| # The checkups nothing else triggers: weekly on Tuesday, plus the daily security-release on the other days. |
Rewrite the comment to describe the schedules as they actually are.
Same posture as developerz-ai/wurk and db-mcp-gateway (owner, 2026-11-14: no human
maintenance unless we add new features).
requests changes with a mandatory security pass on auth/OAuth/config/jobs/tools; CLAUDE.md's
NEVER list as non_goals; only breaking_change escalates.
(toolchain bumps included, which Dependabot cannot do). Briefs in .dz/briefs/.
🤖 Generated with Claude Code