GitHub workflow automation via gh CLI for pull requests, stacked PRs, and repository management.
Works with
Provides stacked PR merge workflow: squash-merge the first PR, then rebase and update base branch for each subsequent PR in the chain
Includes conflict detection and manual resolution prompts to prevent silent failures during multi-PR merges
Covers core gh CLI operations: PR creation, status checks, squash/rebase merging, and branch management
Optimized for low context usage by relying
Use gh CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.
# Create a PR from the current branch
gh pr create --title "feat: add feature" --body "Description"
# Squash-merge a PR
gh pr merge <PR_NUMBER> --squash --title "feat: add feature (#<PR_NUMBER>)"
# View PR status and checks
gh pr status
gh pr checks <PR_NUMBER>
When merging a chain of stacked PRs (each targeting the previous branch):
# Rebase next PR's branch onto main, excluding already-merged commits
git rebase --onto origin/main <old-base-branch> <next-branch>
git push --force-with-lease origin <next-branch>
gh pr edit <N> --base main
gh pr merge <N> --squash --title "<PR title> (#N)"
See stacked-pr-workflow.md for full step-by-step details.
| File | Description |
|---|---|
| stacked-pr-workflow.md | Merge stacked PRs into main as individual squash commits |
| Problem | Start With |
|---|---|
| Merge stacked PRs cleanly | stacked-pr-workflow.md |
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongithubExecute the skills CLI command in your project's root directory to begin installation:
Fetches github from callstackincubator/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate github. Access via /github in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.2K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Useful defaults in github — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in github — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for github matched our evaluation — installs cleanly and behaves as described in the markdown.
github has been reliable in day-to-day use. Documentation quality is above average for community skills.
github fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
github is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
github is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added github from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: github is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: github is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 25