Automatically create GitHub issues for specification requirements not yet implemented in code.
Works with
Analyzes specification files to extract all requirements, then checks codebase implementation status for each one
Searches existing issues to prevent duplicates before creating new feature request issues
Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria
Scans related specification files and code patterns to verify whether requi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreate-github-issues-for-unmet-specification-requirementsExecute the skills CLI command in your project's root directory to begin installation:
Fetches create-github-issues-for-unmet-specification-requirements from github/awesome-copilot 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 create-github-issues-for-unmet-specification-requirements. Access via /create-github-issues-for-unmet-specification-requirements 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<p><strong>Automatically create GitHub issues for specification requirements not yet implemented in code.</strong></p>\n<ul>\n<li>Analyzes specification files to extract all requirements, then checks codebase implementation status for each one</li>\n<li>Searches existing issues to prevent duplicates before creating new feature request issues</li>\n<li>Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria</li>\n<li>Scans related specification files and code patterns to verify whether requirements are partially or fully implemented</li>\n</ul>"}}] 23:T515,<h1>Create GitHub Issues for Unmet Specification Requirements</h1>
<p>Create GitHub Issues for unimplemented requirements in the specification at <code>${file}</code>.</p> <h2>Process</h2> <ol> <li>Analyze specification file to extract all requirements</li> <li>Check codebase implementation status for each requirement</li> <li>Search existing issues using <code>search_issues</code> to avoid duplicates</li> <li>Create new issue per unimplemented requirement using <code>create_issue</code></li> <li>Use <code>feature_request.yml</code> template (fallback to default)</li> </ol> <h2>Requirements</h2> <ul> <li>One issue per unimplemented requirement from specification</li> <li>Clear requirement ID and description mapping</li> <li>Include implementation guidance and acceptance criteria</li> <li>Verify against existing issues before creation</li> </ul> <h2>Issue Content</h2> <ul> <li>Title: Requirement ID and brief description</li> <li>Description: Detailed requirement, implementation method, and context</li> <li>Labels: feature, enhancement (as appropriate)</li> </ul> <h2>Implementation Check</h2> <ul> <li>Search codebase for related code patterns</li> <li>Check related specification files in <code>/spec/</code> directory</li> <li>Verify requirement isn't partially implemented</li> </ul>1e:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"$23"}}] 19:[["$","meta","0",{"charSet":"utf-8"}],["$","meta","1",{"name":"viewport","content":"width=device-width, initial-scale=1"}]] 17:nullPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
github/awesome-copilot
github/awesome-copilot
anthropics/claude-code
mblode/agent-skills
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
Registry listing for create-github-issues-for-unmet-specification-requirements matched our evaluation — installs cleanly and behaves as described in the markdown.
create-github-issues-for-unmet-specification-requirements has been reliable in day-to-day use. Documentation quality is above average for community skills.
create-github-issues-for-unmet-specification-requirements reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: create-github-issues-for-unmet-specification-requirements is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for create-github-issues-for-unmet-specification-requirements matched our evaluation — installs cleanly and behaves as described in the markdown.
create-github-issues-for-unmet-specification-requirements reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added create-github-issues-for-unmet-specification-requirements from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in create-github-issues-for-unmet-specification-requirements — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
create-github-issues-for-unmet-specification-requirements is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: create-github-issues-for-unmet-specification-requirements is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 35