Validate GitHub issue requirements, designs, and plans against the codebase.
npx skills add https://github.com/Junroot/Nomat --skill verify-junroot
Please help me install this Agent Skill. Skill: verify Source: https://github.com/Junroot/Nomat/tree/main/.claude/skills/verify Command: npx skills add https://github.com/Junroot/Nomat --skill verify-junroot
GitHub 이슈의 요구사항, 설계, 구현 계획을 코드베이스와 대조 검증하여 다음 단계로 넘어가도 되는지 확인하는 스킬입니다. 검증 결과는 이슈 코멘트로 기록하고 필요 시 요약을 사용자에게 제공합니다.
선택한 이슈에 대해 요구사항, 설계, 구현 계획을 코드베이스와 대조하는 검증 흐름을 시작하고, 결과를 이슈 코멘트로 남긴 뒤 요약 보고를 제공합니다.
High-intent search queries and answers about installing and using this skill.
Validating GitHub issue requirements against a codebase involves checking the requirements, design, and implementation plans for contradictions, missing items, or impossible features before proceeding to the next stage.
Issue design validation is needed before implementation to ensure the proposed design matches the actual codebase, identify conflicts or dependencies, and confirm that acceptance criteria are verifiable.
Checking for duplicate issues and dependency conflicts requires enforcing validation checks against the existing codebase and issue tracker, then proposing corrective actions if safety risks are detected.
Automated issue triage can verify implementation plans by applying validation checks to issue tasks, recording the validation results as issue comments, and providing a summary of whether it is safe to proceed.
The best way to ensure acceptance criteria are verifiable is to validate them against the codebase during the requirement stage, enforcing checks for conflicts and proposing corrective actions when necessary.
Issue validation fails during the design stage when the proposed design contains contradictions, missing dependencies, or un-verifiable acceptance criteria compared to the actual codebase implementation.
TrogonStackEnrich GitHub pull request descriptions by analyzing git history and branch diffs.
DonTiziTranslate GitHub issue specs into incremental implementation plans with tests and commits.
cliffthelinApply type, effort, priority, and area labels to GitHub issues.
baekenoughAnalyze GitHub issues against the codebase and post prioritized triage comments.
