github-workflow
GitHub Workflow
Core principle: Run quality gates BEFORE committing. Stop on failure. Never push failing code.
When to Use
- User has staged files and wants to push
- User asks "what should I do before pushing?"
- User mentions creating PR or feature branch
When NOT to Use
- No staged changes - user hasn't run
git add - Direct commits to main/master - feature branches only
- User explicitly wants to skip checks
Gotchas
Environment-specific facts that defy reasonable assumptions:
More from melodypapa/uncertainty
sync-req
Use when creating or maintaining ISO/IEC/IEEE 29148 requirements with bidirectional traceability between code and requirements. Handles extraction, generation, sync, deviation detection, and test design derivation using ISO 29119-4 techniques.
9req-traceability
Use when requirements need extraction from code, test cases need derivation from requirements, coverage gaps need analysis, or traceability between requirements, code, and tests is required. Triggers for UNCOVERED_REQ, STALE_TEST, TEST_DRIFT, requirements-code deviations, ISO 29148/29119-4 compliance, or user mentions 'requirements out of sync' or 'test coverage'.
9