pow-software/gh-issue-specifier
skills/gh-issue-specifier/SKILL.md
Analyze a GitHub issue in depth and produce a detailed specification based on codebase analysis. Use when given a GitHub issue URL or number and asked to deeply analyze requirements, scan the repository, and write a structured spec (no code changes).
$ install --global
skillsauthnpx skillsauth add pow-software/bytesync gh-issue-specifierInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:34 PM0.5s1 file scanned
SKILL.md
- name:
- gh-issue-specifier
- description:
- Analyze a GitHub issue in depth and produce a detailed specification based on codebase analysis. Use when given a GitHub issue URL or number and asked to deeply analyze requirements, scan the repository, and write a structured spec (no code changes).
Gh Issue Specifier
Overview
Build a deep, code-informed specification from a GitHub issue using gh CLI and targeted repository analysis. Ask clarifying questions when needed, then deliver a structured, implementation-ready spec.
Workflow
- Parse the issue target
- Accept a full GitHub issue URL or an issue number.
- Resolve owner/repo from the URL when provided.
- If only a number is provided, ask which repo to use.
- Fetch issue details via gh
- Always use
gh issue view <number> --repo <owner>/<repo>. - Capture title, body, labels, and comments.
- Scan the codebase deeply
- Use
rgfor fast discovery (types, references, UI strings, tests, configs). - Open and read relevant files with
Get-Content. - Trace the end-to-end flow: entry points -> services -> domain -> storage -> UI.
- Identify existing validations, error handling, localization, and logging patterns.
- Identify gaps and impacts
- What is missing relative to the issue requirements?
- Which modules and layers must change?
- What new tests are required and where?
- Identify risk areas and backward compatibility issues.
- Ask clarifying questions when needed
- Ask only the minimum set of questions to disambiguate scope, UX, or behavior.
- If no questions are needed, proceed directly to the spec.
- Produce the specification
- Provide a clear, structured spec with concrete behaviors and impacted areas.
- Do not propose code or patches.
Required Spec Format
Include these sections in order:
- Summary
- Scope (In/Out)
- Functional Requirements
- Non-Functional Requirements
- UX / Messaging / Localization
- Logging / Telemetry
- Edge Cases / Error Handling
- Affected Components (files/areas)
- Test Plan (unit/integration/e2e)
- Migration / Compatibility (if applicable)
- Open Questions
- Risks
Operational Notes
- Always use
gh issue view(no browser). - Always use
rgfor discovery before opening files. - Prefer short file excerpts and paraphrase; avoid pasting large blocks.
- Keep the spec actionable and grounded in the current codebase.
Example Trigger Phrases
- "Analyze issue 260 and write a detailed spec"
- "Deeply analyze this GitHub issue and the codebase"
- "Create a specification from https://github.com/<org>/<repo>/issues/<id>"
Related Skills
pow-software/perform-implement-plan
development
VerifiedTrustedCommunity
Execute an implementation plan end-to-end in the ByteSync repo. Use when the user asks to implement a previously established plan step by step, requires creating a branch before coding, expects regular commits during progress, and wants build/test validation.
153SKILL.mdUpdated Apr 24, 2026
pow-software/implementation-plan
development
VerifiedTrustedCommunity
Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.
153SKILL.mdUpdated Apr 24, 2026
pow-software/create-pr
data-ai
VerifiedTrustedCommunity
Push the current branch and create a Pull Request for ByteSync. Use when the user wants the agent to push a branch and open a PR, and requires the PR title and description in English.
153SKILL.mdUpdated Apr 24, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026