framework_eng/skills/framework-meta/quick-fix/SKILL.md
MUST use WHEN the task is classified as simple (< 20 lines, 1 file, no new metadata objects, no architectural decisions). Provides a short cycle of 3 steps with a guard on the self path and mandatory verify.
npx skillsauth add steelmorgan/1c-agent-based-dev-framework quick-fixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Three steps without cross-review. One file, < 20 lines, no architectural decisions, no new features, no new metadata objects.
The Lead (main flow) has classified the task as simple (see orchestrator profile, Layer 1) and chosen the short cycle. In the short cycle, the Lead may execute it personally or delegate one subagent under the guard below.
self execution is the only mode where the main flow has no cross-review. Therefore the boundaries are strict and are checked BEFORE any modification starts.
< 20 lines, 1 file, no new metadata objects, no architectural decisions;navigate_symbol + get_call_graph → path to the module, dependencies, confirm that the change is localized
(confirmation of the guard boundaries: one file, no architectural links).
The minimum necessary change according to coding-standards. No "improvements" beyond the task scope.
get_diagnostics — quick check of the changed filerun_tests — if there are tests for the modulecheck_syntax — final check before commit| Situation | Action | |----------|----------| | Tests fail after the change | Fix or escalate to full | | Multiple modules / architecture / review / > 20 lines / new metadata object | full cycle |
Escalation protocol: record the state → the orchestrator itself raises the phase prompt.
The orchestration discipline and the phase form are already durable in its profile (framework/subagents/orchestrator.md,
Layer 2); it reads the detailed phase mechanics from framework/workflows/full-cycle.md upon entering the phase.
This is NOT "handing off to an external document" and NOT starting another session — the Lead simply puts on the hat
of the full-cycle orchestrator and proceeds with Phase 1 (or Phase 3, if the spec already exists).
depends_on:
development
1C server maintenance webhooks: container restart and external component cache cleanup
development
Interactive DAP debugging of a single BSL procedure
tools
Rules for using RLM tools for project search and navigation in 1C/BSL
development
Creates web applications and routes on Winow (a web server on OneScript and Autumn). Use when working with a web server on OneScript, routing, or Winow controllers.