mirror of
https://github.com/vladmandic/automatic
synced 2026-09-18 16:54:33 +02:00
@@ -130,4 +130,4 @@ If critical information is missing, explicitly list unknowns and what to inspect
|
||||
|
||||
- Prefer concrete evidence from repository files and model card over assumptions.
|
||||
- If source suggests multiple possible paths, compare at least two and state why one is preferred.
|
||||
- Keep recommendations aligned with the conventions defined in the port-model skill.
|
||||
- Keep recommendations aligned with the conventions defined in the port-model skill.
|
||||
|
||||
@@ -148,4 +148,4 @@ A full pass requires all of the following in audited scope:
|
||||
- reference entries are valid, categorized correctly, and have preview files
|
||||
- custom pipeline contracts are consistent with actual model behavior
|
||||
|
||||
If any area is intentionally out of scope, mark as partial pass with explicit exclusions.
|
||||
If any area is intentionally out of scope, mark as partial pass with explicit exclusions.
|
||||
|
||||
@@ -146,4 +146,4 @@ The check passes only if all are true:
|
||||
- each `SamplerData` entry is correctly mapped and usable
|
||||
- no blocking runtime or compile-path failures in validated scope
|
||||
|
||||
If scope is partial due to environment limitations, report pass with explicit limitations, not a full pass.
|
||||
If scope is partial due to environment limitations, report pass with explicit limitations, not a full pass.
|
||||
|
||||
@@ -214,4 +214,4 @@ When closing the task, report which of these were completed:
|
||||
- "The new model port fails in from_pretrained"
|
||||
- "SD.Next detects my custom pipeline as the wrong model type"
|
||||
- "The loader works but generation returns black images"
|
||||
- "This standalone-script port loads weights but crashes in attention"
|
||||
- "This standalone-script port loads weights but crashes in attention"
|
||||
|
||||
@@ -29,8 +29,8 @@ If activation fails, report the blocker and stop before running Python-based too
|
||||
Run tools in this exact sequence:
|
||||
|
||||
1. `pre-commit run --all-files`
|
||||
2. `eslint . javascript/`
|
||||
3. `cd extensions-builtin/sdnext-modernui && eslint . javascript/`
|
||||
2. `{PROJECT_ROOT}/node_modules/.bin/eslint . javascript/`
|
||||
3. `cd extensions-builtin/sdnext-modernui && {PROJECT_ROOT}/node_modules/.bin/eslint . javascript/`
|
||||
4. `ruff check`
|
||||
5. `pylint *.py`
|
||||
6. `pylint modules/`
|
||||
@@ -38,6 +38,8 @@ Run tools in this exact sequence:
|
||||
8. `pylint scripts/`
|
||||
9. `pylint extensions-builtin/`
|
||||
|
||||
Note that `pylint` can run for considerable time, so run with no timeouts.
|
||||
|
||||
## Fix Policy
|
||||
|
||||
- Fix issues reported by each tool before moving on.
|
||||
|
||||
@@ -6,12 +6,12 @@ argument-hint: "Optionally specify state (open/closed/all), max issues, and whet
|
||||
|
||||
# Summarize SD.Next [Issues] GitHub Issues
|
||||
|
||||
Fetch issues from the SD.Next GitHub repository that contain `[Issues]` in the title, then produce a concise markdown report with one entry per issue.
|
||||
Fetch issues from the SD.Next GitHub repository that contain `[Issue]` in the title, then produce a concise markdown report with one entry per issue.
|
||||
|
||||
## When To Use
|
||||
|
||||
- The user asks for periodic issue triage summaries
|
||||
- You need an actionable status report for `[Issues]` tracker items
|
||||
- You need an actionable status report for `[Issue]` tracker items
|
||||
- You want suggested next actions for each matching issue
|
||||
|
||||
## Repository
|
||||
|
||||
@@ -244,4 +244,4 @@ When using this skill, the final implementation should usually include:
|
||||
- "Port this standalone inference script into an SD.Next Diffusers pipeline"
|
||||
- "Add support for this Hugging Face model repo to SD.Next"
|
||||
- "Wire this upstream Diffusers pipeline into SD.Next autodetect and loading"
|
||||
- "Convert this single-file checkpoint model into a custom Diffusers pipeline for SD.Next"
|
||||
- "Convert this single-file checkpoint model into a custom Diffusers pipeline for SD.Next"
|
||||
|
||||
Reference in New Issue
Block a user