fechar-fase

Closes numbered development phases by updating documentation, running validations, and committing changes.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/octanutri-clin/octaclin --skill fechar-fase-octanutri-clin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fechar-fase
Source: https://github.com/octanutri-clin/octaclin/tree/main/.claude/skills/fechar-fase
Command: npx skills add https://github.com/octanutri-clin/octaclin --skill fechar-fase-octanutri-clin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The OctaClin project evolves through numbered phases, and each phase is only complete after a strict sequence of documentation updates, validations, commits, and pushes. This Skill ensures no step of that closing checklist is skipped, keeping the project's continuity rules enforced. ## Core Features & Use Cases - Phase Documentation: Creates or updates the phase file (fase-XXX-*.md) and marks the phase as done in CHECKLIST_FASES_FUTURAS_PRODUCAO.md. - Proportional Validation: Runs typecheck, tests, build, and security checks scaled to the risk areas touched by the phase. - Safe Commit & Push: Commits only reviewed files with an objective message, blocking secrets, real .env files, and database dumps. - Use Case: After finishing a new scheduling feature, ask to close the phase and the Skill updates the checklist, runs backend and frontend validations, commits, pushes, and suggests the next phase. ## Quick Start Ask the assistant to close the current OctaClin phase, for example by saying "fechar a fase 12" after finishing its implementation.

Frequently Asked Questions about fechar-fase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close a development phase in the OctaClin project?▼

Closing a phase requires updating the phase file, marking the checklist item, running proportional validations, and committing with a push. This Skill walks through each step in order so no required documentation or validation is skipped.

What validations should run before committing a phase?▼

Run pnpm typecheck for backend and web, relevant backend test specs, web authz tests, web build, and the secrets security scan. Phases touching permissions, multi-tenant, integrations, backup, or staging require the extra checks listed in TESTES_E_VALIDACOES.md.

When should RESUMO_FASES_CONCLUIDAS.md be updated?▼

Update it only when the phase consolidates a product capability such as a new screen, flow, or integration. Purely internal or documentation-only phases can skip this file.

Can I use git add -A when committing a phase?▼

No. The project forbids git add -A or git add . without review because commits must never include secrets, real .env files, database dumps, or logs with credentials. Stage only the reviewed relevant files.

What happens if a phase is skipped or done out of order?▼

Phases must not be skipped without an explicit user decision. The Skill updates the roadmap to the next numbered phase in the checklist unless the user explicitly changes the order.