Automated summary
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 completing changes to gwexpy and needing a structured validation and commit process.
For trivial changes that don't require full validation, or if you prefer manual commits.
Security analysis
SafeThis 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
How this analysis is madeExamples
Execute the full wrap-up procedure for gwexpy, including physics review, tests, lint, docs sync, directory hygiene, and commit.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
-
Physics Review (if relevant)
- If the change affects physics/math behavior, run
check_physics. - Otherwise, skip and note why.
- If the change affects physics/math behavior, run
-
Tests
- Run
test_code(fullpytest). - If it is too slow, split into logical subsets and report coverage.
- Run
-
Lint/Type Checks
- Run
lint(ruff check .andmypy .).
- Run
-
Docs Sync
- Run
sync_docsto align docstrings and docs (EN/JA) with code changes.
- Run
-
Directory Hygiene
- Run
organizeto confirm no misplaced files. - If tests created
tests/.home/, remove it and addtests/.home/to.gitignoreviaignore.
- Run
-
Commit
- Run
git_committo clean caches and commit with a concise conventional message. - Do not delete non-standard files without confirmation.
- Run
-
Report
- Summarize tests/lint results and whether full pytest completed.
- Provide commit hash if created.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/wrap-up-gwexpy-mmk3ni75/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/wrap-up-gwexpy-mmk3ni75' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/wrap-up-gwexpy-mmk3ni75/download' --output '.skill-downloads/wrap-up-gwexpy-mmk3ni75/SKILL.md.part' && mv '.skill-downloads/wrap-up-gwexpy-mmk3ni75/SKILL.md.part' '.skill-downloads/wrap-up-gwexpy-mmk3ni75/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/wrap-up-gwexpy-mmk3ni75/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.