nextstage-brasil · Agent Skills

4 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

nextstage-brasil

Community

ns-autonomous

(NS) Autonomous execution engine — plans depth, resolves doubts from docs/specs, multi-agent work in an isolated worktree. Use for a local/pasted plan or "run this autonomously" without GitLab. Also Phase 2 under ns-execution-gitlab-issue (do not run standalone then). Not for single-step edits (ns-coder) or GitLab issues directly (ns-execution-gitlab-issue).

installazioni

1

GitHub Stars

0

Aggiornato

24 ott

Apache-2.08 File

Vedi dettagli →

nextstage-brasil

Community

ns-best-practices

(NS) Security/compat/a11y + Vercel Web Interface Guidelines. Use when hardening security, fixing CSP/CORS/headers, reviewing UI / checking a11y / auditing UX, or Web Interface Guidelines — even without saying \"best practices\"; also ns-proto-creator close-out. Do NOT use for MR/SOLID (ns-reviewer), visual redesign (ns-frontend-design), or features (ns-coder / ns-spec-driven).

installazioni

1

GitHub Stars

0

Aggiornato

24 ott

Apache-2.04 File

Vedi dettagli →

nextstage-brasil

Community

ns-bug-report-diagnosis

(NS) Diagnose a product bug report (screen, expected vs actual, ticket, screenshot description) by tracing the reported flow across every layer the consumer stack has. Chat-only eight-section report, then auto-dispatch ns-execution-gitlab-issue (ISSUEURL) or ns-coder unless the user opted out (diagnose-only / do not fix). This skill does not write the patch. Use whenever the user pastes a relato, issue, ticket, screenshot description, \"what is happening\", \"diagnose this\", expected vs actual

installazioni

1

GitHub Stars

0

Aggiornato

24 ott

Apache-2.06 File

Vedi dettagli →

nextstage-brasil

Community

ns-gitlab-board-sync

(NS) Sync existing GitLab issues with local planning/execution — milestone, RF labels, status, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always atomic setissuelabels and three-step status cycle.

installazioni

1

GitHub Stars

0

Aggiornato

24 ott

Apache-2.03 File

Vedi dettagli →