Skip to content

docs: offer a fixed-scope setup under the audit - #55

Merged
renezander030 merged 1 commit into
masterfrom
docs/setup-offer
Oct 28, 2026
Merged

renezander030 merged 1 commit into
masterfrom
docs/setup-offer

Conversation

@renezander030

Copy link
Copy Markdown
Owner

Problem

The 14-day GitHub traffic shows 105 unique cloners against 45 unique viewers and 0 external dependents (read 2026-10-25): people take the code, but the repo gives them no way to ask for help adopting it, so interest never becomes a named user or a setup request.

Change

  • README: a short "Want it set up for your team?" block right under the one-command audit, where the audit's findings are fresh. It offers a fixed-scope setup (done.yaml, agent hooks, server-side CI gate), quoted in days, with no price on the page.
  • .github/ISSUE_TEMPLATE/setup_request.yml: a "Setup request" issue form (agents used, audit output, CI host, what done means), labelled setup-request, so a request is countable on the demand board. Email stays as the private route.

Verified

  • npm ci && npm run build && npm test: 257 pass, 0 fail
  • node dist/src/cli.js check: all 4 gates pass
  • The issue form parses as YAML.

Note: the setup-request label does not exist in the repo yet; GitHub drops a missing label silently, so create it once after merge for the count to work.

🤖 Generated with Claude Code

… issue form

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014hMK4M4JSpXc6cutN8aFw1
@renezander030
renezander030 enabled auto-merge (squash) October 28, 2026 13:05
@renezander030
renezander030 merged commit 423b9c9 into master Oct 28, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant