github-issue-standard

What This Skill Does

The github-issue-standard skill acts as a strict governance agent for the OpenClaw platform, ensuring that every GitHub issue generated within the SpecWeave ecosystem adheres to a rigorous, traceable, and machine-readable format. It prevents the creation of "orphaned" issues by enforcing the mandatory use of Feature-based prefixes ([FS-XXX][US-YYY]) and validating the inclusion of critical metadata like acceptance criteria, task tracking, and absolute GitHub URLs. By centralizing the issue documentation standard, it eliminates technical debt caused by inconsistent naming conventions and broken dependency chains between specs and codebase increments.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-github-issue-standard Once installed, the OpenClaw agent will automatically invoke these validation checks whenever a GitHub issue creation request is processed.

Use Cases

• Requirement Traceability: Use this whenever you are mapping a new user story to a specific Feature Spec to ensure auditors can trace the work from requirements to code.
• Automated Issue Generation: When the agent automates the creation of tickets from SpecWeave documents, this skill ensures the title and body metadata are compliant with the github-client-v2 validation layer.
• Maintenance & Refactoring: Use this when refactoring legacy tickets to ensure they link properly to their parent increments and specifications.

Example Prompts

1. "Create a GitHub issue for the 'Auth Header Update' task. It falls under FS-059 and is user story US-003. Include ACs: AC-US3-01 (P1, testable)."
2. "Format this technical debt issue for FS-054 regarding the Reopen Desync Bug. Ensure all links point to the current develop branch increment 0042."
3. "Review the current issue draft. Does it meet the standard? I have included the checkable task list and the correct FS-XXX prefix structure."

Tips & Limitations

• Tip: Always cross-reference your Feature ID (FS-XXX) with your increment folder (e.g., Increment 0031 implies FS-031). If they do not match, the system may flag a logic error.
• Tip: Use absolute URLs for all GitHub links as relative paths will break in the issue description view.
• Limitation: This skill cannot automatically resolve semantic conflicts in acceptance criteria; it only validates the structural presence and format of the criteria. You must still define the actual testable logic correctly.