← all publishers

gualask

@gualask source repo

Report this profile Claim this profile

• 12 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Cf Test · gualask bundle

   Report assertion-quality and test-contract findings for changed or explicitly targeted tests. Use when the request asks to review test quality, coverage against requirements or invariants, brittle or over-specified tests, implementation-detail coupling, negative assertions, or domain-invalid states representable by the project's types or schemas. Do not use to run or fix tests or to review production code generally; route structural change-set review to cf-review and behavior ambiguity to cf-scenario.
   0
   installs
2. ▌
   Cf Todo · gualask

   Create or update a lightweight todo file tracking next steps and open questions from an analysis or working session. Use when the request asks to write, add to, update, or check off a todo.md, or to record remaining work and open questions in a tracking file. Do not use to read an existing todo file or to answer what it contains. Do not use for Cflow refactor progress or resume state (cf-start owns them), or for project documentation (cf-docs).
   0
   installs
3. ▌
   Cf Split · gualask bundle

   Evaluate or execute a behavior-preserving file-level split from one source file into nearby owned files. Use when the current request asks whether a file should be split or asks to perform a scoped extraction into files. Route regrouping of multiple related files to cf-cohesion and repository-level restructuring to cf-start.
   0
   installs
4. ▌
   Cf Start · gualask bundle

   Assess and plan repository-level refactors: architecture, structure, ownership, dependency direction, target shape, migration order, execution, review, verification, and `.cflow` resume. Use after the diagnostic frame is confirmed. Do not use for a bounded fix, a security or correctness defect confined to a few files, or any change that does not move ownership, structure, or dependency direction.
   0
   installs
5. ▌
   Cf Review · gualask bundle

   Report structural, convention, and authoritative requirement findings for a set of code changes. Use only when the current request explicitly asks for a review of pending work, recent commits, a commit range, or a branch. Do not use to fix findings, assess test assertion quality, or review an unchanged file or area; route test quality to cf-test and a target without a change set to the owning diagnostic skill.
   0
   installs
6. ▌
   Cf Mr Wolf · gualask bundle

   Recover the goal behind a reported symptom, or the shape of a change nobody has decided yet. Use when the user reports a symptom, an experience, or a doubt without naming what should change, or asks what a change would consist of while its shape is still open — even when the target is already named. Do not use once the request names both its target and the change to make to it, even when voiced as a doubt: a named component with its technical alternatives, a proposal whose worth or impact is the question, a bounded edit, a defect whose fix is one localized edit, or code review.
   0
   installs
7. ▌
   Cf Cohesion · gualask bundle

   Evaluate or execute behavior-preserving local regrouping of already-related files into a cohesive feature or workflow slice. Use when the problem is navigation cost, placement, scattered files, feature-slice cohesion, or whether related files should live together. Do not use for non-code content; route single-file splits to cf-split and repository-level restructuring to cf-start.
   0
   installs
8. ▌
   Cf Deadcode · gualask bundle

   Report which code is dead or unreachable. Use when the request asks whether code is unused, dead, no longer needed, or can be deleted. Do not use it to remove that code, and do not use it during a review or a refactor that has not asked about unused code.
   0
   installs
9. ▌
   Cf Scenario · gualask bundle

   Decide a named change against the scenarios it touches. Use when the request names both a thing and the change to make to it — remove this, merge these two, keep it as it is — and asks whether it is worth doing or what it would cost elsewhere. A doubt counts when it names both: "these two look almost identical, worth merging?", "this abstraction looks overengineered, can it go?". Do not use when nothing is named to change and the request only asks what currently happens, nor for a repository map or structural inventory.
   0
   installs
10. ▌
    Cf Cognitive · gualask bundle

    Find or refactor local source-file cognitive complexity hotspots while preserving behavior. Use when a function or file is hard to read or reason about — overloaded functions, deep nesting, tangled branching, local readability pressure — with or without explicit file targets. Do not use to split a file into new files (cf-split) or for repository-wide refactors (cf-start).
    0
    installs
11. ▌
    Cf Brainstorm · gualask bundle

    Turn a feature or product idea into an approved design spec before any implementation. Use only when the user explicitly asks to brainstorm, explore, or co-design an idea; never trigger it from implementation requests, bug fixes, refactor work, or other Cflow flows. Do not use for ambiguous requests, approach questions, or worth-building judgments.
    0
    installs
12. ▌
    Cf Docs · gualask bundle

    Write accurate, lean, nonduplicative documentation. Use when the request writes a Markdown file — authoring, updating, trimming, or restructuring docs, READMEs, or design notes — or asks to audit or fact-check them against the code; do not use otherwise.
    0
    installs