ttncode

codeignitor3-simplifier

Simplifies and refines PHP/CodeIgniter 3 code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

codeigniter3-simplifier

Use when refining recently-changed PHP/CodeIgniter 3 code for clarity and consistency without changing behavior.

unioss-brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

unioss-bump-migration

Use when bumping a UNIOSS migration timestamp, reindexing files, and updating the migration config and tests.

unioss-generate-migration

Use when the user asks to generate migration files for the UNIOSS project.

Use when a ticket's GitLab merge request(s) received review comments — verify each against current code, then on approval apply fixes, run the suite, commit, and push. Run as /unioss-mr-feedback <mr-url>.

Testing & QA Listed

unioss-phpunit-test

Use when writing, updating, or debugging PHPUnit tests for UNIOSS CodeIgniter modules.

unioss-plan

Use when turning a UNIOSS investigation into an implementation plan with exact per-file changes, estimate points, and per-step verification — the planner stage.

unioss-review

Use when diff-reviewing the UNIOSS coder's changes against clean-code, CI3, plan-adherence, and security standards — the reviewer stage; outputs a severity-indexed report.

unioss-scope

Use when writing or updating the PM/QC-facing scope.md for a finished UNIOSS ticket.

unioss-ship

Use when shipping a finalized UNIOSS ticket — pushes the feature branch and opens merge requests into staging or customer staging; never merges. Run as /unioss-ship.

unioss-writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

unioss-executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

unioss-receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

unioss-requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

unioss-subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

unioss-test-evidence

Use when the tester stage builds its test-case set — derives cases mechanically from changes.md + spec ACs + scope.md, and enforces per-case evidence and an honest PASS/PARTIAL/FAIL verdict.

unioss-knowledge-ask

Answer a free-form question about UNIOSS 3 tickets/comments for any period, from stored knowledge; refresh first only when stale.

unioss-knowledge-refresh

Crawl + distill the current window into the knowledge base (daily WWWH; weekly/monthly/yearly two-phase sentiment + GLOBAL).

unioss-api-spec

Use when a change adds or alters a UNIOSS API endpoint and you need a house-format API spec, or standalone via /unioss-api-spec.

unioss-gitlab-issue-context

Use when you need to fetch or refresh a GitLab ticket's data (writes raw-ticket-data.json + ticket-summary.md) — standalone or as the investigator's ticket-fetch step.