changegate
/changegate
Ocenia, czy żądana zmiana w oprogramowaniu jest potrzebna, rozróżniając zachowanie poprawne, częściowo naprawione, zepsute, brakujące i niejasne.
- Autor
- piyush2707 ↗
- Repozytorium
- Change-gate ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 02.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 02.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Ocenia, czy żądana zmiana w oprogramowaniu jest potrzebna, rozróżniając zachowanie poprawne, częściowo naprawione, zepsute, brakujące i niejasne.
Oryginalny opis (EN)
Evaluate whether a requested software change is necessary before modifying code. Distinguish already-correct, partially fixed, broken, missing, and unclear behavior. Use for bug reports, feature requests, code improvements, and refactoring requests.
Jak działa
- Decision workflow
- Reference documents
- Required final report
- Critical safeguards
Podgląd SKILL.md
--- name: changegate description: Evaluate whether a requested software change is necessary before modifying code. Distinguish already-correct, partially fixed, broken, missing, and unclear behavior. Use for bug reports, feature requests, code improvements, and refactoring requests. --- # CHANGEGATE Think before you change. Determine whether a requested software change is necessary before implementing it. Do not assume every request requires code modifications. ## Decision workflow ### 1. Understand Identify the requested outcome, expected behavior, current behavior, and relevant requirements. ### 2. Inspect Before editing: - Read relevant implementation files. - Inspect related functions and components. - Examine existing tests. - Check relevant configuration and documentation. - Search for existing implementations. - Inspect project history when useful. Do not assume code exists merely because a filename suggests it does. ### 3. Evaluate Compare actual behavior with the requested outcome. Determine whether the behavior is: - Already correct. - Partially implemented. - Incorrect. - Missing. - Impossible to determine with available evidence. - Ambiguous and requiring clarification. ### 4. Classify Select exactly one primary decision: **NO_CHANGE** The requested outcome already exists and available evidence supports that conclusion. **PARTIAL_FIX** Some requested behavior works, but identifiable requirements remain incomplete. **CHANGE_REQUIRED** The requested behavior is absent or demonstrably incorrect. **INVESTIGATE** More evidence is needed before making a reliable decision. **CLARIFY** The request contains ambiguity that materially affects implementation. ### 5. Explain Report the selected decision and supporting evidence before implementation. ### 6. Act - NO_CHANGE: Stop without unnecessary edits. - PARTIAL_FIX: Complete only the missing behavior. - CHANGE_REQUIRED: Implement the smallest suitable change. - INVESTIGATE: Gather more evidence. - CLARIFY: Ask one focused question. Respect user instructions and environment permissions. ### 7. Verify When changes are made: - Inspect the diff. - Run relevant tests when available. - Check for unintended modifications. - Report actual verification results. Never claim tests passed unless they were actually run. ## Reference documents The following reference files are expected alongside this SKILL.md: - `references/decision-rules.md` - `references/evaluation-cases.md` Read `references/decision-rules.md` before classifying a request. Read `references/evaluation-cases.md` when evaluating decision quality or testing edge cases. ## Required final report ### CHANGEGATE Decision **Decision:** NO_CHANGE / PARTIAL_FIX / CHANGE_REQUIRED / INVESTIGATE / CLARIFY **Requested outcome:** Describe what the user wanted. **Evidence:** Summarize relevant code, behavior, tests, or observations. **Reasoning:** Explain the decision. **Action taken:** Describe the action or explain why no changes were made. **Verification:** Report actual tests and results. Identify anything not verified. ## Critical safeguards - Never invent evidence. - Never invent test results. - Never assume an existing function is correct. - Never ignore partially completed fixes. - Never modify unrelated files. - Never silently expand task scope. - Never reject necessary changes just to minimize edits. - Never claim this skill provides a security boundary. The objective is to make the correct change — and avoid the unnecessary one.
Pliki w paczce (3)
- SKILL.md 3 KB
- references/decision-rules.md 5 KB
- references/evaluation-cases.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · piyush2707/Change-gate | 90 | MIT |
| piyush2707/Change-gate | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki a0c350d1979c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
Brak podobnych skilli w bazie.