Wrap Up gwexpy

VerifiedSafe

Performs a complete sequence of validation, cleanup, and commit for gwexpy projects. Coordinates physics checks, testing, linting, documentation sync, and file organization.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude CodeCursorWindsurfCopilotCodex
#gwexpy#end-of-workflow#validation#housekeeping#commit

Recommended for

Our review

Runs a series of checks and cleanups (tests, lint, docs sync, directory hygiene, commit) to finalize work on the gwexpy project.

Strengths

  • Automates the entire wrap-up process from validation to commit
  • Ensures code quality through tests, lint, and type checks
  • Synchronizes documentation and cleans up temporary files
  • Generates a concise conventional commit message

Limitations

  • Specific to the gwexpy project and assumes other skills are available
  • May be slow if the test suite is large
  • Requires confirmation before deleting non-standard files
When to use it

When you have completed changes to gwexpy and want to validate, clean up, and commit your work.

When not to use it

For minor changes that don't require full validation, or when working outside the gwexpy project.

Security analysis

Safe
Quality score75/100

The skill only orchestrates other typical development skills (testing, linting, documentation, git commit) and contains no dangerous commands, exfiltration, or obfuscation. It explicitly advises caution with file deletion.

No concerns found

Examples

Full wrap-up after changes
I've made some changes to gwexpy. Please run the full wrap-up: physics review, tests, lint, docs sync, directory hygiene, and commit.
Wrap-up without physics review
Perform the gwexpy wrap-up but skip the physics review since my changes don't affect physics.

name: wrap_up_gwexpy description: gwexpy向けの一連の検証・整理・コミット手順をまとめて実行する

Wrap Up (gwexpy)

This skill performs a full end-of-workflow wrap-up for gwexpy, aligned to available skills.

Instructions

  1. Physics Review (if relevant)

    • If the change affects physics/math behavior, run check_physics.
    • Otherwise, skip and note why.
  2. Tests

    • Run test_code (full pytest).
    • If it is too slow, split into logical subsets and report coverage.
  3. Lint/Type Checks

    • Run lint (ruff check . and mypy .).
  4. Docs Sync

    • Run sync_docs to align docstrings and docs (EN/JA) with code changes.
  5. Directory Hygiene

    • Run organize to confirm no misplaced files.
    • If tests created tests/.home/, remove it and add tests/.home/ to .gitignore via ignore.
  6. Commit

    • Run git_commit to clean caches and commit with a concise conventional message.
    • Do not delete non-standard files without confirmation.
  7. Report

    • Summarize tests/lint results and whether full pytest completed.
    • Provide commit hash if created.
Related skills