Menu
Install or upgrade Fini CLI from the latest GitHub release assets.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | fini-setup |
| description | Install or upgrade Fini CLI from the latest GitHub release assets. |
Use when fini is missing, broken, outdated, or needed for agent terminal use.
Use these before doing a general web search:
https://github.com/VRuzhentsov/fini/releases/latesthttps://api.github.com/repos/VRuzhentsov/fini/releases/latestFor a requested version, use the matching release page instead of latest.
Choose a standalone CLI asset from the release assets for the current system. The asset should match OS and CPU architecture and should be a CLI archive, not a GUI installer.
Common release families:
finifini.exeLet the current system decide the exact detection method: uname, PowerShell, environment variables, package metadata, or another reliable local signal.
fini already works: command -v fini and fini --help.tmp/ directory or a platform-provided runtime directory..sig as verified unless the release also provides public verification material or instructions.--help.PATH, or ask if multiple locations are plausible.fini --help command.--help.TRIGGER when user asks to create, update, list, or manage quests, spaces, reminders, or Focus state in Fini. Use the `fini-cli` foundation skill for binary preflight, CLI/app mode selection, JSON output decisions, and safe command sequencing before any action.
Always use this at the start of development work in the Fini repo. Orchestrates which repo-local or gstack skill to load, which Makefile command to prefer, what context to read, and what evidence is required before claiming implementation, debugging, QA, Android, design-to-code, release, or documentation work is complete.
Use this skill for Fini major release preparation, especially when the user asks for Play Store screenshots, Android marketplace screenshots, store listing assets, release screenshot packages, or "major release prep". This skill should trigger even if the user only mentions screenshots, because Fini's canonical store assets live in `docs/play-store/` and must be generated, checked, and reported consistently before a release.
Run and maintain Fini's GitOps release workflow. Use this whenever the user asks to make a release, bump a release version, push a release tag, inspect release readiness, fix release automation, or verify release CI. Releases are initiated by pushing a signed annotated v* tag; `make release` must run `make pre-release-check` before any version commit, branch push, or tag push.
Single source of truth for testing the Fini app: how to run unit, integration, and end-to-end tests, and how to write new ones. Use when the user asks to run tests, write a test, add coverage, debug a failing test, choose a test category, set up a multi-actor scenario, or understand fixtures and harnesses. For Android-only behavior, load `fini-android-testing` instead. For CLI semantics referenced from CLI e2e tests, also load `fini-cli`. For Makefile/CI/script changes around tests, also load `fini-scripting`.
Fini Vue frontend implementation conventions for views, templates, rendering decisions, and tests.