Skip to content

docs(skills): add spec-start-github for issue-driven spec PRs#821

Open
ifireball wants to merge 1 commit into
fullsend-ai:mainfrom
ifireball:cursor/spec-start-github-skill
Open

docs(skills): add spec-start-github for issue-driven spec PRs#821
ifireball wants to merge 1 commit into
fullsend-ai:mainfrom
ifireball:cursor/spec-start-github-skill

Conversation

@ifireball
Copy link
Copy Markdown
Contributor

Summary

  • Add skills/spec-start-github/SKILL.md: thin GitHub layer (issue fetch, canonical prompt, agent/<issue>-spec-* branch rules, commit + local gh pr create vs harness handoff) that defers the headless spec procedure to spec-start (no duplicated checklist/templates).
  • Update skills/spec-start/SKILL.md with cross-links so the two skills are paired for issue-driven runs.

Context

Implements fullsend-ai/fullsend#803 (sub-issue of planning-oriented agents / spec workflows).

Verification

  • make lint (staged skill files) passed locally.

Made with Cursor

Add a thin skill that binds spec-start to GitHub (issue as canonical
prompt, agent/<issue>-spec-* branches, local gh pr create vs harness
post-script). Cross-link from spec-start for pairing.

Closes fullsend-ai#803

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions
Copy link
Copy Markdown

fullsend review is working on this — view logs

@github-actions
Copy link
Copy Markdown

Site preview

Preview: https://faf39b28-site.fullsend-ai.workers.dev

Commit: f441e1b437a9b1c4f8c10640040aa0ccd10e31db

@ifireball ifireball self-assigned this May 12, 2026
@fullsend-ai-review
Copy link
Copy Markdown

Review: #821

Head SHA: f441e1b
Timestamp: 2026-05-12T00:00:00Z
Outcome: approve

Summary

Clean documentation-only PR that adds the spec-start-github skill as a thin GitHub layer (issue fetch, branch conventions, commit and PR mechanics) on top of the existing spec-start skill, with proper bidirectional cross-links. The change matches the scope of issue #803, follows existing skill patterns (frontmatter, structure, naming), and includes good safety measures (branch collision detection, scan-secrets guidance, harness vs local mode separation). No findings across any review dimension.

Findings

No findings.

Footer

Outcome: approve
This review applies to SHA f441e1b437a9b1c4f8c10640040aa0ccd10e31db. Any push to the PR head clears this review and requires a new evaluation.

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