CodeIssuesDiscussionsWikiPull RequestsProjectsCommitsActionsReleasesContributorsPulse● GatesSecurityDeploymentsPipelineInsightsAgents✨ Explain✨ Ask AI✨ Workspace✨ Spec✨ Tests▓ Debt Map✨ NL Search🏛 Archaeology
✨ AI Workspace
Claude-powered coding modes for demo/design-docs. 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 →
○[triage] Investigate flaky tests in design-docs#12
○[AI] Add /metrics endpoint to design-docs#11
○Clarify ADR-001 rollout section#6
○Welcome to GlueCron#5
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.