alwaysmeticu
10 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
alwaysmeticulousmeticulous-cli
Overview of the Meticulous CLI tool and its global options. Use when asking about the meticulous CLI in general, available commands, or global flags that apply to all commands.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 15 de out.
alwaysmeticulousmeticulous-cli-update
Check whether the Meticulous CLI (@alwaysmeticulous/cli) and skills are installed and up to date, and install/update them if not. Invoked at the start of every other Meticulous skill, since the CLI and skills are under active development with frequent changes and improvements.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-fix
Fix the visual diffs (and any non-visual checks) that have been reviewed and rejected on a Meticulous test run, following their review comments if given, plus any Agent swarm fix prompts on the same commit. Use when a user has reviewed the results of a test run and is handing off to an agent to implement the fixes.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 15 de out.
alwaysmeticulousmeticulous-increase-coverage
Increase coverage for a Meticulous project by tracing specific under-covered files back to a real UI action in the codebase, driving that action with a real recorded browser session, and validating the improvement with a clean coverage comparison. Also opens a PR proposing .meticulousignore entries for code that structurally never executes in-browser. Use when asked to "increase coverage", "find untested code", or "add .meticulousignore entries" for a project.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-iterative-dev
Iterative frontend development loop using Meticulous for per-step visual validation. Use when implementing a multi-step frontend change and want to catch visual regressions and unintended side effects at each step, before the final cloud test run.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-review
Work through a Meticulous test run's results, reacting to their review state — review the unreviewed diffs (and any failing non-visual checks) against what the PR is meant to change, flagging potential regressions; when you're working on the PR's code, hand what needs fixing (diffs someone rejected or commented on, and your own rejections) to the meticulous-fix skill; also summarizes any Agent swarm results. Resolves the test run from the local repo's current commit (the default), or from an exp
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-simulate-and-diff
Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a base replay. Use when checking whether a code change has introduced visual regressions for a specific session.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 15 de out.
alwaysmeticulousmeticulous-test
Run a Meticulous test run after implementing a frontend change, then hand off to the meticulous-review skill to classify each visual change as intended or unintended. Uploads the build once — the same build can be re-triggered against different bases without rebuilding — and it works with uncommitted changes. Use when implementing a feature autonomously end-to-end before creating a PR.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-use-session-data
Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.
alwaysmeticulousmeticulous-zero-diff-task
Implement a task for which no visual diffs are expected end to end, using Meticulous to drive the implementation to a clean visual diff before opening a PR. Use when the task's whole premise is "the UI shouldn't change" — a dependency/version upgrade, a code refactor, a migration, or similar. Meticulous isn't just a final check here, it's the loop you iterate against while implementing.
- instalações
- 2
- GitHub Stars
- 10
- Atualizado
- 22 de out.