CodeIssuesPull RequestsActionsSecurityInsights
✨ AI
More
Settings
✨ AI Workspace
Claude-powered coding modes for ccantynz/Gluecron.com. Describe what you want built — the AI writes the code, opens a branch, and creates a draft PR for review.
📋
Spec-to-PR
Paste a feature specification in plain English. Claude analyses the codebase, writes the implementation, and opens a draft pull request ready for your review.
Write a spec →
🔧
Fix an issue
Pick any open issue below. Claude reads the issue, explores the relevant code, writes a fix, and opens a PR — you just review and merge.
Browse open issues ↓
✏️
Web editor
Edit files directly in the browser. Great for quick documentation updates, config tweaks, or small fixes without cloning the repo.
Open editor →
🧪
Generate tests
Point Claude at a file or function. It generates a test suite, creates a branch, and opens a PR so you can review coverage improvements instantly.
Generate tests →
Open issues — launch AI workspaceAll issues →
autorepair wrote an empty commit directly to a repo's default branch#218
Workflow secrets are text-substituted into the command string, so leaking one is the natural thing to write#217
Reliability tier 2: SLO dashboard, dedicated CI runner, mirror-schedule keepalive#214
CI: re-include the 21 excluded test files (subprocess PATH + env-sensitive audits)#213
Incident 2026-08-08: merges from stale branches replaced main and discarded five merged PRs (fixed; regression test needed)#212
Visual design audit: full-site ledger (every page viewed, 2026-08-08)#211
Review-first conflict resolution: AI-resolved merges should land on the head branch for review, not inside the merge commit#210
Non-git onboarding: WordPress (and other no-git) users cannot get code into Gluecron#209
Best specs get best results
Include acceptance criteria, the affected files if you know them, and any constraints (no new dependencies, must stay backwards-compatible, etc.).
Always review the diff
AI PRs are drafts. Claude marks them clearly with an ⚡ AI badge. Check the diff before merging — gates still run so broken builds are caught automatically.
Issues → specs → PRs
The fastest flow: file a clear issue, use "Fix with AI" to start a workspace, review the resulting PR. The gate CI runs automatically on every push.