uinaf/ffss
The flipflopslopstack skill set: review with slopguard, deliver, babysit, plan, maintain docs, prepare repos, equip stack skills, audit agent setups, and de-slop.
Configure GitHub settings, collaboration files, Actions, releases, and deployments. Use for setup or changes to those surfaces; excludes provider infrastructure and product code.
Review or replace React useEffect calls, or enforce a no-direct-effect policy. Use for effect implementation, refactoring, or lint policy; excludes unrelated React work and non-React effect systems.
Audit a person's whole agentic setup: loaded rules and skills, how they are actually used in session logs, recent shipped work, and the repositories, machines, MCP servers, and pipelines agents touch. Use for a periodic retro or when asked what to prune, fix, or add in an agent workflow; not for reviewing one change or auditing one codebase.
Remove AI tells from prose, code, or tests when asked to unslop or humanize an artifact, or prune low-value tests from a suite; preserve meaning, behavior, and coverage.
Open or update a change request for completed, verified work, including its title, body, and review aids. Use whenever creating, drafting, or editing a pull or merge request, or deciding what follows once one is open. Not for resolving review feedback or CI on an open one.
Review a code change with the slopguard CLI when the user asks for it, or when the repository has no automated review on change requests, and handle its results: validate findings, fix accepted issues, and write the review closeout.
Resolve review feedback and CI on an open change request, merge when green unless asked to hold, then watch the runs the merge starts. Use for babysitting delivered work.
Inspect or improve repository and runner readiness for autonomous work, including boot, verification, and recovery.
Update repository documentation and agent guidance against current sources when fixing drift or cleaning up docs.
Select and install repository-local skills for the current stack and task. Use when setting up a repo, checking skill coverage, or preparing work with missing stack guidance.
Record agreed future work in the repository's tracker when asked to file an issue, track this for later, save a plan for another session, or break work into tickets; not for in-session checklists or doing the work now.