Feature · Execution
From opportunity to GitHub issue in one click.
Most SEO tools tell you 'fix this page'. Slope writes the spec, attaches the evidence, and files the GitHub issue — so a developer (or an AI coding agent like Claude Code) can act on it without re-doing the analysis.
What
What it does
When you approve an opportunity in Slope and click 'Push to GitHub', we create an issue in the repo of your choice. The issue body contains: the opportunity summary, the evidence that triggered it (specific GSC metrics, page URL, current CTR vs target, etc.), and a recommended-actions list specific enough to ship. We also set labels and attach a comment back with the Slope opportunity URL so the loop is traceable.
Why it matters
The job to be done
- AI coding agents (Claude Code, Cursor agents, OpenAI Codex CLI, Devin, Aider) work great on well-scoped GitHub issues — Slope writes the kind of issue they can act on.
- Your dev team already lives in GitHub. They don't want another dashboard. Pushing to where work happens beats asking them to come to where analysis happens.
- Audit trail. The issue creator shows as 'Slope' (a GitHub App, not a user), so anyone reviewing the repo history can see exactly what was suggested vs what was implemented.
- Short-lived tokens. Slope uses GitHub App installation tokens (max 1 hour lifetime) — we never see your personal access tokens, and you can scope the App to specific repos.
- Round-trip status. When you close the issue in GitHub, Slope marks the opportunity as completed. After 14 days, we measure GSC impact and write it back to the task.
How
What happens under the hood
- 1
Install the GitHub App
From Integrations → GitHub, click 'Install GitHub App'. You choose which repos to grant access to. Slope stores only the installation ID — no PAT, no secret on your side.
- 2
Approve an opportunity
On the Opportunities page, review the suggestion + evidence. If you like it, click 'Push to GitHub'. Pick the destination repo. Done.
- 3
Issue gets created
Slope mints an installation token (JWT-signed with our App's private key), creates the issue via GitHub's REST API, attaches labels (slope:opportunity, slope:low_ctr, etc.), and stores the issue URL on the execution_task record.
- 4
Measure impact
When the issue closes in GitHub (your webhook fires), Slope marks it completed. 14 days later, the impact worker queries GSC for clicks/impressions/position delta on the target URL and writes it back to the task. You see the actual outcome of the fix.
Related features
Start finding opportunities tonight.
Connect your domain, GSC, and GitHub. First detection runs within minutes. Free tier requires no card.