Search

PythonReactSEOPDF
GitHub Skill

verify

Use before claiming work is complete - run verification commands and confirm output

TKontu☆ 0 Repository stars0 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

Verification Before Completion

The Rule

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Before Saying "Done"

  1. Run the tests

    pytest
    

    Must see: All pass, 0 failures

  2. Run the linter

    ruff check .
    

    Must see: No errors

  3. Check types (if applicable)

    mypy src/
    

    Must see: Success

Evidence Format

When reporting completion:

Verification:
- pytest: 47/47 passed
- ruff check: 0 errors
- mypy: Success

Red Flags

If you're thinking:

  • "Should work now" - RUN IT
  • "I'm confident" - RUN IT
  • "Just this once" - NO, RUN IT

Never

  • Claim tests pass without running them
  • Say "should work" instead of verifying
  • Skip verification because you're confident
  • Trust previous runs - run fresh

Checklist

Before PR/commit:

  • pytest run, output shows all pass
  • ruff check run, output shows clean
  • No errors or warnings
  • Actually read the output, don't just run

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-20
Index updated
2026-01-26
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!