Faye Coding Assistant

Plugin faye-coding-assistant in Fayegram-AI/plugin-market. Commands read from the repo's manifest — 4 days ago.

Skills (14)

• code-review

  Use for a requested general review of a diff, PR, branch, module, or named code surface, including when fixes are also requested; not for phased review, concrete-failure diagnosis, or suite health. Establish findings before authorized remediation.

• codebase-exploration

  Use only when a repository map, trace, explanation, or pre-change impact analysis is a requested deliverable; not for reads that merely support another workflow. Covers ownership, architecture, execution or data flow, dependencies, and configuration.

• coding-goal-guardrails

  Use for a new multi-step coding /goal, explicitly resuming an interrupted, paused, or blocked goal, or a guardrails request; not for ordinary active-goal continuation, validation, milestones, or final reporting.

• coding-handoff

  Prepare requested handoffs, including PR descriptions and continuation context, from supplied facts or bounded change evidence. Exclude ordinary status/completion/plan briefings, delivery, implementation, and independent diagnosis or review. Read-only.

• phase-implementation-review

  Use when the current request asks to review a completed phase, cumulative phased work, or the final phased result, including when fixes are requested; not for accepted-plan self-review or checkpoints. Establish findings before authorized remediation.

• reconcile-repository-docs

  Use to reconcile repository-wide documentation with current repository state, typically after development or before release; not for incidental docs work or a bounded document edit. It may update docs within scope.

• refactor-planning

  Use for a requested restructuring or compatibility migration plan, including before authorized execution; not when new behavior is primary or for verification-only planning. The planning stage does not edit.

• report-coding-goal-progress

  Use for a requested milestone, status, or completion report from an authoritative active, blocked, or just-completed coding /goal snapshot; not for automatic checkpoints, plan briefings, or general project status.

• repository-change-planning

  Use for a requested repository change plan: create, assess, or materially revise it, including before authorized execution. Exclude briefings, accepted-plan execution, incidental planning, and refactor/verification-only plans. Planning does not edit.

• repository-debugging

  Use to diagnose concrete failures, unexpected behavior, or unusually slow tests, builds, runtime, CI, or commands, including requests to fix them; not for speculative review or suite health. Fix only when explicitly requested.

• repository-implementation

  Use for a bounded repository edit, including accepted-plan execution, its embedded self-review, or remediation after review or suite assessment; not for the preceding analysis, concrete-failure debugging, or repository-wide docs reconciliation.

• source-file-token-estimation

  Use only when explicitly requested to estimate the approximate token footprint of large repository source, test, or debug files or compare line-chunk split scenarios. This read-only workflow does not measure actual Codex usage.

• test-suite-health

  Use to assess suite-wide test cost, flakiness, overlap, isolation, or maintainability, including before authorized remediation; not for failure diagnosis, test-code correctness, change verification, or source-file token estimation. Assessment does not edit.

• verification-planning

  Plan requested test coverage, checks/commands, or manual QA, including before authorized execution. Exclude suite health, named-command execution, already-specified test edits, and incidental verification. Planning does not edit or run checks.

Similar plugins