tticom
- 12 skills
- 0 followers
- 9 hours ago last updated
- ▌ Code Review · tticom bundleReview a live pull request, or the changes since a fixed point (commit, branch, tag, or merge-base), along two separate axes: Standards (documented coding standards plus a code-smell contract) and Spec (fidelity to the originating issue or specification). Pins the exact head, enforces comment-only reviewer authority, and publishes the formal verdict, inline findings, and a marked summary to the PR. Use when asked to review a PR, a branch, or work in progress, or to review since a commit.
- ▌ Hard Review · tticom bundlePerform an exact-head hard review that includes the complete basic code review plus adversarial inspection of test-data provenance, real-world acceptance evidence, oracle independence, and production-code fixture coupling. Use for conversion fidelity, parsers, geometry, timing, matching, generated artifacts, private fixtures, empirical claims, or whenever synthetic, mocked, generated, or data-free tests could create false confidence.
- ▌ Dispatch Task · tticom bundleDetermine and dispatch the next authorised action in a governed project. Locates the project's configured task authority, inspects live task, PR, and review state, identifies the responsible role, and either runs the project's configured dispatcher or produces a concrete handoff. Stops when configuration or authority is missing, conflicting, or records that no task is approved. Use only when the user explicitly asks to continue, advance, dispatch, or run the next governed task.
- ▌ Durable Handoff · tticom bundleWrite a durable, repository-owned handoff tied to exact revisions and evidence without duplicating specs, diffs, or reports. Use when work must survive conversation loss, cross agent or identity boundaries, accompany a PR, or record the state of a governed development task.
- ▌ Changes Requested · tticom bundleAddress CHANGES_REQUESTED review verdicts on open pull requests. Ingest reviewer findings, reproduce defects on the reviewed head, apply minimal safe fixes, verify regressions, and hand back with evidence.
- ▌ Governance Author · tticomAuthor or revise governed task promotions, active-task records, role-specific prompts, and control-plane PRs. Use when a project separates governance from product work, assigns identities or repositories by role, promotes a candidate into executable authority, or needs to prevent stale state, self-promotion, repository-ownership drift, and non-discriminating governance tests.
- ▌ Identity Safe Git · tticom bundleVerify operating-system, home, Git-host, commit, workspace, and branch identity before repository mutations, then enforce branch-safe Git and PR operations. Use with multiple agent accounts, isolated clones, protected branches, automation identities, or policies that allow feature pushes but prohibit direct main pushes, force pushes, self-approval, or merges.
- ▌ Workspace Cleanup · tticom bundleSafely remove stale review worktrees and prune dead worktree metadata across the Git checkouts in an agent workspace, preserving any dirty, locked, unclassified, or unverified work, and record a receipt and checkout index. Use when asked to clean up the workspace, remove stale review worktrees, or produce a map of the workspace checkouts.
- ▌ Publish Pr Handback · tticom bundleValidate and atomically publish a complete exact-head pull-request author handback. Use after an author pushes a new or revised PR head in a review-gated workflow, before claiming a review-ready state, or when repeated stale or malformed handback comments leave a dispatcher waiting.
- ▌ Devils Advocate Review · tticomPerform the complete basic and hard reviews while presuming every developer claim, handback, test conclusion, and earlier reviewer approval is wrong until independent attempts fail to disprove it. Use for high-risk changes, disputed or repeatedly revised PRs, prior false approvals, governance handoffs, conversion correctness, or when the user asks for a real, adversarial, devil's-advocate, or final review.
- ▌ Verified Implementation · tticom bundleImplement a specification or set of tickets with evidence-gated completion, meaning captured test results, no false green, provenance-classified inputs, a traced final effect, and a clean-head pre-flight before handback. Use when implementing specified work that another identity will review independently, or when completion claims must be backed by executed evidence.
- ▌ Governed Development Loop · tticom bundleExecute a versioned, review-gated development task without conflating project policy with reusable workflow mechanics. Use when a repository has an active-task pointer or approved prompt, fixed scope, validation contract, separate author/reviewer identities, or a one-PR-at-a-time development loop.