- Home
- Skills
- Steveclarke
- Dotfiles
- Finalize
finalize_skill
- Shell
31
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
1 month ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill steveclarke/dotfiles --skill finalize- SKILL.md3.5 KB
Overview
This skill runs a post-implementation finalization checklist to ensure code, docs, visuals, and issue hygiene are ready before committing or merging. It is designed for shell-based projects and projects that include a project-specific CLAUDE.md with finalization requirements.
How this skill works
The skill executes a universal checklist: lint/format, tests, code-quality sweep, documentation, UI/design verification, git/issue hygiene, and memory updates when applicable. After the universal pass it reads the project's CLAUDE.md for a "Finalize Checklist" section and runs any project-specific items found. Wherever possible the skill fixes issues directly instead of only reporting them, and it reports remaining items that require manual attention.
When to use it
- When you say: "finalize" or "final review"
- Before creating a pull request or merging: "ready to merge"
- Before pushing changes from a local machine: "preflight check"
- When wrapping up a feature or bugfix: "wrap this up"
- If you suspect something was missed: "did we miss anything"
Best practices
- Run lint/format tools listed in project files (package.json, Gemfile, CLAUDE.md) and apply fixes automatically when safe
- Run full test suite and ensure no unexpected skips; add tests for new behavior or note why tests are omitted
- Remove debug statements, TODO/FIXME markers, and hardcoded secrets; replace with constants or utilities
- Align new UI code with the project component library and spacing/typography tokens; verify responsive and accessibility basics
- Update PR description, link issues (Closes #N), and create follow-on issues for deferred work
Example use cases
- Finish a set of shell scripts and ensure formatting and tests pass before merging
- Finalize a UI tweak: verify component usage, spacing scale, color tokens, and run visual checks in dev server
- Wrap up a refactor by scanning for dead code, updating docs, and ensuring tests cover changed behavior
- Prepare a cross-machine sync toolset: run shell lint, confirm docs reflect install steps, and add memory notes about chosen defaults
- Close out a bugfix: run tests, confirm PR links the issue, and create follow-ups for related edge cases
FAQ
Yes — where safe (formatting, lint fixes, removing obvious debug lines) the skill applies fixes. It reports any risky changes for manual review.
How does it find project-specific finalization steps?
It scans CLAUDE.md for a "Finalize Checklist" or similar section and executes each listed item after completing the universal checklist.