ttncode
User🚀 An A→Z, human-gated ticket pipeline for the UNIOSS team. A GitLab ticket in — an investigated, planned, coded, reviewed, tested, ship-ready change out.
Categories
Indexed Skills (28)
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
Use before any creative work on UNIOSS code — GATE 0 clarification, feedback rounds, and ad-hoc UNIOSS tasks. Explores intent, requirements and design against the UNIOSS codebase 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.
unioss-mr-feedback
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>.
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 structuring a UNIOSS implementation plan from an approved UNIOSS spec — the plan format the unioss-planner stage emits and the unioss-implement coder applies.
unioss-executing-plans
Use when executing a written UNIOSS implementation plan in a separate session with batch checkpoints. Standalone alternative to the gated /unioss-pipeline flow — inside that flow the coder is unioss-implement at GATE 2.
unioss-receiving-code-review
Use when evaluating review feedback on UNIOSS code — GATE 3 findings and GitLab MR comments — before implementing any suggestion. Requires verifying each claim against the current code, not performative agreement.
unioss-requesting-code-review
Use when requesting a whole-branch code review of UNIOSS work before merging — the standalone reviewer dispatch. Inside the gated /unioss-pipeline flow the diff review is unioss-review at GATE 3 instead.
unioss-subagent-driven-development
Use when executing a UNIOSS implementation plan task-by-task in the current session, dispatching a fresh subagent per task with review between tasks. Standalone alternative to the gated /unioss-pipeline flow — inside that flow the coder is unioss-implement at GATE 2.
unioss-test-evidence
Use when the tester stage builds its test-case set — derives black-box cases mechanically from changes.md + spec ACs + scope.md across three layers, enforces the risk-gated exception taxonomy, per-case evidence, failure severity, 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 ticket reports; weekly/monthly/yearly two-phase sentiment + GLOBAL).
unioss-knowledge-report
How to write a valuable ticket report from ticket evidence — structure, method, depth modes, user's language. Read before writing any today/ticket/daily report.
unioss-doctor
Use when checking or repairing the UNIOSS pipeline's environment on this machine — dependencies, config, module paths, browser permission.
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.
unioss-knowledge-approve
Review staged prescriptive rules and promote the approved ones into the live rules + GLOBAL.
unioss-feedback
Continue a shipped UNIOSS ticket from customer feedback — opens a new round (does not restart A→Z).
unioss-task
Run the UNIOSS pipeline on an ad-hoc request that has no GitLab ticket.
unioss-knowledge-ticket
Full report (user's language) for one GitLab ticket — evidence out, agent analysis (ticket + codebase) in.
unioss-knowledge-today
Report today's new UNIOSS 3 tickets — evidence out, agent-written reports in the user's language.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.