agentleFS
Sign inStart free
HarryJhinHarryJhin/groundwork/skills/verification-before-completion/SKILL.md

verification-before-completion

Skill0 starsChanged 3 months agoMITView on GitHub

Use before claiming a change is complete, a bug is fixed, or a check passed.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259
  • +4 more from jh941213

The file

Create a free account to mount
Files
SKILL.md

verification-before-completion

Verify the claim

입력은 하려는 주장과 대상 변경이다. 요청·설계의 완료 기준을 리포 설정·CI와 대조해 그 주장을 판정할 검증 방법을 정한다. 테스트 인프라가 없어도 실행·관측·정적 검사 등 변경에 맞는 방법을 선택한다. 서비스의 완료 기준이 미정이면 groundwork:finding-unknowns로 확인한다.

검증을 실행하고 종료 코드·출력·검사 범위를 확인한다. 현재 대상 트리와 범위가 같은 기존 증거는 재사용할 수 있으며, 이후 변경이 영향을 준 검사는 다시 실행한다. 부분 검사로 전체 성공을 주장하지 않는다. 버그 수정은 원래 증상이 재현되는 검사로 확인하고, 회귀 테스트는 수정 전 실패·수정 후 통과를 확인한다. 위임한 구현은 실제 diff와 요구를 대조한다. 보고된 검증은 대상 커밋·명령·결과를 확인하고, 증거가 부족한 부분을 검증한다.

Report the evidence

실행한 검사와 결과, 확인하지 못한 범위·실패·잔여 문제를 보고한다. 검증 수단이 없거나 검사가 실패하면 그 상태를 밝히고 통과를 주장하지 않는다.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free