busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

tasks and workflow updated

Browse Source
This commit is contained in:
busya
2026-01-29 10:06:28 +03:00
parent d4109e5a03
commit 8044f85ea4
11 changed files with 156 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
specs/017-llm-analysis-plugin/checklists/data-integrity.md
View File

@@ -5,14 +5,14 @@
**Created**: 2026-01-28
## Requirement Completeness
- [ ] CHK001 Are requirements defined for mapping generated documentation to the correct metadata fields? [Completeness, Spec §FR-017]
- [x] CHK001 Are requirements defined for mapping generated documentation to the correct metadata fields? [Completeness, Spec §FR-017]
- [ ] CHK002 Are requirements specified for handling schema changes during documentation generation? [Completeness, Gap]
- [ ] CHK003 Are requirements defined for validating the format of the generated commit message? [Completeness, Gap]
- [ ] CHK004 Are requirements specified for concurrent documentation updates? [Completeness, Gap]
## Requirement Clarity
- [ ] CHK005 Is "structured description" defined with specific markdown or text constraints? [Clarity, Spec §SC-004]
- [ ] CHK006 Are "recent commit history" requirements defined by count or time window? [Clarity, Spec §FR-012]
- [x] CHK006 Are "recent commit history" requirements defined by count or time window? [Clarity, Spec §FR-012]
## Edge Case Coverage
- [ ] CHK007 Are requirements defined for when the LLM generates hallucinated column names? [Edge Case, Gap]

16
specs/017-llm-analysis-plugin/checklists/reliability-security.md
View File

@@ -5,12 +5,12 @@
**Created**: 2026-01-28
## Requirement Completeness
- [ ] CHK001 Are retry strategies (count, backoff) defined for all external LLM API calls? [Completeness, Spec §FR-018]
- [ ] CHK002 Are timeout thresholds specified for long-running validation tasks? [Completeness, Gap]
- [ ] CHK003 Are encryption requirements defined for storing API keys at rest? [Completeness, Spec §FR-002]
- [x] CHK001 Are retry strategies (count, backoff) defined for all external LLM API calls? [Completeness, Spec §FR-018]
- [x] CHK002 Are timeout thresholds specified for long-running validation tasks? [Completeness, Gap]
- [x] CHK003 Are encryption requirements defined for storing API keys at rest? [Completeness, Spec §FR-002]
- [ ] CHK004 Are masking requirements defined for displaying API keys in the UI? [Completeness, Gap]
- [ ] CHK005 Is the fallback behavior defined when the primary screenshot method (Headless) fails? [Completeness, Spec §FR-016]
- [ ] CHK006 Are requirements defined for handling rate limits from LLM providers? [Completeness, Gap]
- [x] CHK005 Is the fallback behavior defined when the primary screenshot method (Headless) fails? [Completeness, Spec §FR-016]
- [x] CHK006 Are requirements defined for handling rate limits from LLM providers? [Completeness, Gap]
- [ ] CHK007 Are data privacy requirements specified regarding what dashboard data (screenshots, logs) is sent to the LLM? [Completeness, Gap]
## Requirement Clarity
@@ -19,6 +19,6 @@
- [ ] CHK010 Is "automatic retry logic" defined with specific backoff parameters? [Clarity, Spec §FR-018]
## Edge Case Coverage
- [ ] CHK011 Are requirements defined for scenarios where the LLM provider is completely unreachable? [Edge Case, Gap]
- [ ] CHK012 Are requirements defined for handling "token limit exceeded" errors with large logs? [Edge Case, Gap]
- [ ] CHK013 Are requirements defined for invalid/expired API keys during task execution? [Edge Case, Gap]
- [x] CHK011 Are requirements defined for scenarios where the LLM provider is completely unreachable? [Edge Case, Gap]
- [x] CHK012 Are requirements defined for handling "token limit exceeded" errors with large logs? [Edge Case, Gap]
- [x] CHK013 Are requirements defined for invalid/expired API keys during task execution? [Edge Case, Gap]

8
specs/017-llm-analysis-plugin/checklists/ux-usability.md
View File

@@ -7,9 +7,9 @@
## Requirement Completeness
- [ ] CHK001 Are requirements defined for the "Validate" button state during active execution (loading/disabled)? [Completeness, Gap]
- [ ] CHK002 Are feedback requirements defined for successful/failed connection tests in Settings? [Completeness, Gap]
- [ ] CHK003 Are requirements specified for viewing historical validation reports? [Completeness, Spec §US1]
- [ ] CHK004 Are requirements defined for the notification content layout (summary vs. link)? [Completeness, Spec §FR-015]
- [ ] CHK005 Are requirements defined for the "Generate Commit" interaction flow (modal vs. inline)? [Completeness, Spec §US4]
- [x] CHK003 Are requirements specified for viewing historical validation reports? [Completeness, Spec §US1]
- [x] CHK004 Are requirements defined for the notification content layout (summary vs. link)? [Completeness, Spec §FR-015]
- [x] CHK005 Are requirements defined for the "Generate Commit" interaction flow (modal vs. inline)? [Completeness, Spec §US4]
## Requirement Clarity
- [ ] CHK006 Is "visual representation" defined with resolution or format constraints? [Clarity, Spec §FR-005]
@@ -20,5 +20,5 @@
- [ ] CHK009 Are error messages consistent with the application's existing error handling standards? [Consistency, Gap]
## Edge Case Coverage
- [ ] CHK010 Are requirements defined for when a dashboard cannot be rendered (e.g., 404)? [Edge Case, Gap]
- [x] CHK010 Are requirements defined for when a dashboard cannot be rendered (e.g., 404)? [Edge Case, Gap]
- [ ] CHK011 Are requirements defined for when the generated commit message is empty or invalid? [Edge Case, Gap]