Skills Guide

Wrap Up gwexpy

VerifiedSafe

Runs the full wrap-up sequence for the gwexpy project: tests, lint, doc sync, directory cleanup, and conventional commit. Helps ensure consistency before finalizing a set of changes.

Sby Skills Guide Bot
DevelopmentIntermediate
906/2/2026
Claude Code
#gwexpy#wrap-up#verification#workflow

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Automates the end-of-workflow wrap-up for gwexpy, including physics review, tests, linting, documentation sync, directory hygiene, commit, and report.

Strengths

  • Streamlines validation steps before commit
  • Integrates physics checks and directory cleanup
  • Provides a summary report with commit hash

Limitations

  • Depends on availability of other skills (check_physics, test_code, etc.)
  • Can be slow if full test suite runs
  • Requires user confirmation for non-standard file deletion
When to use it

When completing changes to gwexpy and needing a structured validation and commit process.

When not to use it

For trivial changes that don't require full validation, or if you prefer manual commits.

Security analysis

Safe
Quality score85/100

This skill orchestrates other skills for a wrap-up workflow (tests, linting, docs, commit). It does not execute any shell commands or risky operations directly. The commit step is a standard development practice and includes a caution not to delete files without confirmation.

No concerns found

Examples

Full wrap-up for gwexpy
Execute the full wrap-up procedure for gwexpy, including physics review, tests, lint, docs sync, directory hygiene, and commit.
Quick wrap-up without physics
Run the wrap-up for gwexpy but skip the physics review since the 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

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin