devendra-skill-package 1.0.2

package/.github/skills/code-test-coverage-analyzer/assets/status-definitions.md

@@ -0,0 +1,273 @@
+# Status Definitions — Project Requirements Compliance Auditor
+
+These are the authoritative definitions for every status value used in the compliance reports.
+Do NOT interpret these definitions loosely. Apply them exactly as written.
+
+---
+
+## Feature / BRD Requirement Status
+
+### IMPLEMENTED
+**Definition**: The requirement is fully and correctly implemented. All aspects of the requirement
+are present in the source code. The implementation produces the behavior described in the
+requirement without gaps.
+
+**Evidence Requirement**: Must cite at least one file path and one function, class, or component
+that directly implements the requirement.
+
+**When to use**: ONLY when you have read the actual implementing code and confirmed all aspects
+of the requirement are present.
+
+**NOT acceptable**: Marking IMPLEMENTED because a file name suggests it, because an API endpoint
+seems related, or because a similar feature exists.
+
+---
+
+### PARTIALLY_IMPLEMENTED
+**Definition**: Implementation exists but covers only part of the requirement. The gap is specific
+and documented. The implementation is correct for what exists, but something required is missing.
+
+**Evidence Requirement**: Must cite what IS implemented (with file/function) AND what is missing
+(with specific description of the gap).
+
+**When to use**:
+- Feature exists but one of several required fields is missing
+- API is called but response is not fully mapped
+- Validation exists but error message is wrong
+- Screen exists but required UI elements are missing
+- Business rule exists but one condition branch is not implemented
+
+**Coverage %**: Estimate what fraction of the requirement is covered (e.g., 60% if 3 of 5 aspects
+are implemented).
+
+---
+
+### MISSING
+**Definition**: No implementation found anywhere in the repository after exhaustive search.
+The feature, screen, API, validation, or business rule does not exist.
+
+**Evidence Requirement**: Must state "Searched using strategies S1–S6 (per assets/multi-strategy-search.md):
+{list each strategy and result}. No implementation found across {N} strategies."
+
+**When to use**: Only after ALL applicable strategies in `assets/multi-strategy-search.md` have returned
+no results. The minimum bar is all six strategies, or all strategies applicable to the requirement type
+as defined in multi-strategy-search.md §Minimum Strategies by Requirement Type.
+
+Two search strategies is never sufficient. Always follow the full six-strategy protocol.
+
+**NOT acceptable**: Marking MISSING after one or two searches. The six-strategy protocol is mandatory.
+See `assets/multi-strategy-search.md` for the full protocol and evidence recording format.
+
+---
+
+### INCORRECT
+**Definition**: Implementation exists but contradicts or violates the requirement. The code does
+something different from what was specified — not just incomplete, but actively wrong.
+
+**Evidence Requirement**: Must cite the requirement's expected behavior AND the actual code's
+behavior, with file path and function name.
+
+**When to use**:
+- Required field maximum is 10 characters but implementation allows 20
+- Required API uses POST but implementation uses GET
+- Required navigation goes to ScreenA but implementation goes to ScreenB
+- Required calculation formula is different from implemented formula
+- Required error message says X but implementation says Y (use INCORRECT for systematic error,
+  use PARTIALLY_IMPLEMENTED if only the message wording is off and everything else is right)
+
+---
+
+### EXTRA
+**Definition**: Implementation found that has no corresponding requirement in BRD, User Stories,
+or Test Cases. Not a defect — reported separately for awareness.
+
+**Evidence Requirement**: Must cite file path. Must confirm no matching requirement found after
+searching all three input documents.
+
+**When to use**: Screens, APIs, features, business rules, or validation rules that exist in code
+but were never requested. This is NOT a failure status — it is an informational flag.
+
+---
+
+### NOT_VERIFIED
+**Definition**: Insufficient evidence in the source code to make a determination. The code is too
+abstract, generated, or obfuscated to confirm whether the requirement is met.
+
+**Evidence Requirement**: Must explain why verification was not possible.
+
+**When to use** (rare, last resort):
+- Code is entirely generated and cannot be inspected
+- Requirement depends on runtime configuration not in source
+- Feature is behind a feature flag and cannot be traced
+- Code uses dynamic imports that cannot be statically analyzed
+
+**NOT acceptable as a default**: NOT_VERIFIED must never be used as a shortcut when a thorough
+search has not been performed.
+
+---
+
+## Test Case Verdict
+
+### PASS
+**Definition**: All test steps can be traced to working implementation. The expected result
+described in the test case matches what the actual code will produce.
+
+**Evidence Requirement**: For each test step, cite the implementing code. For the expected result,
+confirm the code produces that output.
+
+---
+
+### PARTIAL_PASS
+**Definition**: Most test steps are satisfied, but one or more expected results differ from what
+the implementation will produce. The feature exists but has a gap that causes partial failure.
+
+**Evidence Requirement**: List which steps pass (with evidence) and which steps fail (with
+specific reason and what is missing or wrong).
+
+---
+
+### FAIL
+**Definition**: The implementation cannot satisfy the test case. The feature exists but is
+implemented in a way that contradicts the expected result.
+
+**Evidence Requirement**: Cite the specific implementation that produces the wrong behavior.
+State what the expected result is and what the actual implementation produces instead.
+
+---
+
+### NOT_IMPLEMENTED
+**Definition**: The feature or screen or API required to execute this test case does not exist.
+The test cannot even begin because the prerequisite implementation is absent.
+
+**Evidence Requirement**: State what is missing and confirm via search that it does not exist.
+
+**Implication**: Every test case with NOT_IMPLEMENTED verdict means there is also a MISSING
+entry in the BRD/Story compliance reports.
+
+---
+
+### BLOCKED
+**Definition**: This test case cannot be evaluated because it depends on another feature that is
+itself missing or failing. The dependency must be resolved first.
+
+**Evidence Requirement**: Name the blocking dependency (BRD-ID, US-ID, or feature name).
+
+---
+
+### UNKNOWN
+**Definition**: Cannot determine whether the test case passes or fails due to insufficient
+code evidence. Use only when thorough analysis was performed and still inconclusive.
+
+**Evidence Requirement**: Explain what was attempted and why a verdict cannot be reached.
+State what would be needed to make a determination.
+
+---
+
+## Acceptance Criterion Status
+
+### SATISFIED
+**Definition**: The acceptance criterion is fully met. Evidence confirms the described behavior
+exists in the implementation.
+
+---
+
+### PARTIALLY_SATISFIED
+**Definition**: The acceptance criterion is partially met. Some aspects of it are implemented,
+but specific parts are missing or incorrect. The gap is documented.
+
+---
+
+### NOT_SATISFIED
+**Definition**: The acceptance criterion is not met. The implementation does not produce the
+required behavior.
+
+---
+
+### NOT_VERIFIABLE
+**Definition**: Cannot determine from source code alone whether this criterion is satisfied.
+Common for criteria that describe UX behavior, performance, or user perception.
+
+---
+
+## Additional BRD Requirement Statuses
+
+### CONFLICTED
+**Definition**: Two or more source documents (BRD, User Stories, or intra-BRD sections) specify
+contradictory values for the same requirement. The implementation cannot be judged until the
+contradiction is resolved.
+
+**Evidence Requirement**: Cite both conflicting sources with their exact text and values.
+Example: "BRD-014 says max PIN length = 6. US-007-AC-03 says max PIN length = 8. Contradiction."
+
+**Coverage impact**: CONFLICTED requirements score 0% until the conflict is resolved by
+the project team. They appear in a dedicated "Conflicts" table in File 02.
+
+---
+
+### SCOPED_OUT
+**Definition**: This requirement was intentionally excluded from this audit by the user (via Q8).
+It exists in the BRD but is not in scope for the current release or audit session.
+
+**Evidence Requirement**: Reference the user's Q8 input.
+
+**Coverage impact**: SCOPED_OUT items are excluded from the denominator entirely. They appear
+in a separate "Deferred / Out of Scope" section in File 02 and do NOT affect the overall score.
+
+---
+
+## Confidence Levels
+
+Applied to all IMPLEMENTED and PARTIALLY_IMPLEMENTED statuses. Use the decision tree below —
+do not assign confidence intuitively.
+
+### Confidence Decision Tree
+
+```
+Did you open and read the specific file that contains the implementation?
+  YES → Did you find the exact function/component that implements this requirement?
+          YES → Did you read enough of that function to confirm behavior matches requirements?
+                  YES → HIGH confidence
+                  NO  → MEDIUM confidence (function found, not fully traced)
+          NO  → Was the file read but implementation inferred from imports or file name?
+                  YES → MEDIUM confidence
+                  NO  → LOW confidence
+  NO  → Did you find the file path from a grep pattern match (but did not read the file)?
+          YES → MEDIUM confidence (indirect — pattern matched, content not confirmed)
+          NO  → LOW confidence (circumstantial — directory name, related file, similar naming)
+```
+
+### HIGH
+**Criteria**: Directly read the implementing function. Behavior confirmed from source.
+No ambiguity. Cite: file path + function name + line range read.
+
+### MEDIUM
+**Criteria**: Indirect evidence — either read the file but couldn't trace all branches,
+OR found the file via grep but didn't read in full. Implementation strongly inferred.
+Cite: what was read and what was inferred.
+
+### LOW
+**Criteria**: Circumstantial only. File structure, naming, or import graph suggests
+implementation but no direct confirmation. Usually indicates PARTIALLY_IMPLEMENTED or
+NOT_VERIFIED is the more appropriate status.
+
+**Rule**: Status = IMPLEMENTED with LOW confidence is only permitted if there are 3+ independent
+circumstantial signals all pointing to the same conclusion. Otherwise use PARTIALLY_IMPLEMENTED.
+
+---
+
+## Message Match Status (for Validation Analysis)
+
+### EXACT
+Implemented message is character-for-character identical to the required message (case-insensitive
+comparison is allowed; leading/trailing whitespace is trimmed before comparison).
+
+### SIMILAR
+Implemented message conveys the same meaning but with different wording. Still a mismatch — must
+be flagged for review and approval by business stakeholders.
+
+### MISMATCH
+Implemented message is substantially different from the required message. Wrong tone, wrong field
+name, missing field name, or wrong instruction.
+
+### MISSING
+No validation message is displayed. Field may be validated but no user-facing message is shown.

package/.github/skills/code-test-coverage-analyzer/examples/example-invocation.md

@@ -0,0 +1,208 @@
+# Example Invocations — Project Requirements Compliance Auditor
+
+---
+
+## Example 1 — React Native Project
+
+**User invokes**:
+```
+/code-test-coverage-analyzer BRD.md USER_STORIES.md TEST_CASES.md
+```
+
+**Skill asks**:
+```
+COMPLIANCE AUDITOR — CONFIGURATION
+===================================
+Q1  BRD File:          ? (what is the path to your BRD Markdown file?)
+```
+
+**User provides**: `./docs/BRD.md`
+
+**Skill continues collecting Q2–Q5**, auto-detects platform from package.json (ReactNative, Redux Toolkit, Axios).
+
+**Skill presents summary**:
+```
+COMPLIANCE AUDITOR — CONFIGURATION SUMMARY
+===========================================
+Q1  BRD File:          ./docs/BRD.md
+Q2  User Stories:      ./docs/USER_STORIES.md
+Q3  Test Cases:        ./docs/TEST_CASES.md
+Q4  Project Root:      ./
+Q5  Output Folder:     COMPLIANCE_AUDIT_REPORT/
+Q6  Platform:          ReactNative
+Q7  Optional Docs:     None
+
+Estimated scope:
+  Source files to scan:   247
+  Platform patterns:      references/react-native-patterns.md
+
+Type "OK" to begin the audit or "cancel" to abort.
+```
+
+**User types**: `OK`
+
+**Skill begins 12-pass analysis, then generates 14 files.**
+
+**Final output**:
+```
+AUDIT COMPLETE
+==============
+Project: MyBankingApp
+Platform: ReactNative (Redux Toolkit + Axios)
+Output Folder: COMPLIANCE_AUDIT_REPORT/
+
+Input Documents:
+  BRD:          ./docs/BRD.md — 48 requirements parsed
+  User Stories: ./docs/USER_STORIES.md — 22 stories, 87 acceptance criteria
+  Test Cases:   ./docs/TEST_CASES.md — 65 test cases
+
+Files Generated:
+  [01] 01_EXECUTIVE_SUMMARY.md         — 89 lines
+  [02] 02_BRD_COMPLIANCE.md            — 312 lines
+  [03] 03_USER_STORY_COMPLIANCE.md     — 445 lines
+  [04] 04_TEST_CASE_COMPLIANCE.md      — 598 lines
+  [05] 05_VALIDATION_ANALYSIS.md       — 234 lines
+  [06] 06_UI_ANALYSIS.md               — 187 lines
+  [07] 07_API_ANALYSIS.md              — 156 lines
+  [08] 08_BUSINESS_LOGIC_ANALYSIS.md   — 203 lines
+  [09] 09_NAVIGATION_ANALYSIS.md       — 145 lines
+  [10] 10_TRACEABILITY_MATRIX.md       — 178 lines
+  [11] 11_MISSING_FEATURES.md          — 134 lines
+  [12] 12_EXTRA_IMPLEMENTATION.md      — 67 lines
+  [13] 13_COMPLIANCE_SCORECARD.md      — 98 lines
+  [14] 14_FINAL_RECOMMENDATIONS.md     — 156 lines
+
+Overall Compliance Score: 73%
+Risk Level: MEDIUM
+Production Readiness: CONDITIONAL
+
+Placeholder Validation: PASS (0 remaining)
+```
+
+---
+
+## Example 2 — Flutter Project with Optional Docs
+
+**User invokes**:
+```
+/code-test-coverage-analyzer
+```
+
+**Q7 provided**: `./docs/api-swagger.yaml, ./docs/architecture.md`
+
+**Skill incorporates**:
+- `api-swagger.yaml` → used in Pass 3 (API Discovery) to cross-check expected endpoints
+- `architecture.md` → used in Pass 1 (Structure Discovery) to validate actual architecture
+
+---
+
+## Example 3 — Android Project (Pre-populated Paths)
+
+**User invokes**:
+```
+/code-test-coverage-analyzer ./requirements/BRD.md ./requirements/UserStories.md ./requirements/TestCases.md ./MyApp
+```
+
+**Skill auto-fills Q1–Q4 from arguments, only asks Q5 (output folder name).**
+
+---
+
+## Sample Executive Summary Output (excerpt)
+
+```markdown
+# Executive Summary
+Generated by: Project Requirements Compliance Auditor
+Audit Date: 2026-07-07
+Project: /projects/MyBankingApp
+Platform: ReactNative
+
+## Overall Compliance Score
+
+Overall Compliance: 73%
+[====================>                   ] 73/100
+
+## Risk Score
+
+**MEDIUM** — The project has notable compliance gaps but core flows are implemented.
+Non-critical features and some validations are missing.
+
+## Production Readiness
+
+**CONDITIONAL** — Can proceed to UAT with a targeted fix sprint.
+Must resolve Priority 1 blockers (4 items) before production release.
+
+## Coverage at a Glance
+
+| Dimension              | Total | Implemented | Partial | Missing | Coverage % |
+|------------------------|-------|-------------|---------|---------|------------|
+| BRD Requirements       |    48 |          34 |       7 |       7 |      70.8% |
+| User Stories           |    22 |          15 |       5 |       2 |      68.2% |
+| Acceptance Criteria    |    87 |          61 |      14 |      12 |      70.1% |
+| Test Cases (Pass)      |    65 |          43 |      12 |      10 |      66.2% |
+| Validations            |    31 |          24 |       4 |       3 |      77.4% |
+| APIs                   |    18 |          16 |       1 |       1 |      88.9% |
+| UI Screens             |    12 |          10 |       1 |       1 |      83.3% |
+| Business Logic Rules   |    24 |          18 |       3 |       3 |      75.0% |
+| Navigation Flows       |    19 |          14 |       2 |       3 |      73.7% |
+
+## Critical Issues
+
+1. **BRD-023** — Loan Confirmation Screen not implemented (MISSING) — 3 test cases blocked
+2. **BRD-031** — Real-time EMI calculation not displayed before submission (PARTIALLY_IMPLEMENTED)
+3. **BRD-038** — PIN lockout after 3 failed attempts missing (MISSING)
+4. **TC-045** — OTP resend timer does not reset on re-entry (FAIL)
+5. **TC-052** — Aadhaar number validation accepts 11-digit input (INCORRECT)
+```
+
+---
+
+## Sample Validation Analysis Output (excerpt)
+
+```markdown
+#### Field: aadhaarNumber on AadhaarVerificationScreen
+
+| Aspect | Required (from BRD-019) | Implemented (from code) | Match |
+|--------|------------------------|------------------------|-------|
+| Rule | required + exactly 12 digits | required + maxLength=12 (no digit-only check) | MISMATCH |
+| Error Message | "Please enter valid 12-digit Aadhaar number" | "Aadhaar number is required" | MISMATCH |
+| Trigger | onSubmit + onChange | onSubmit only | MISMATCH |
+| File | — | src/screens/kyc/AadhaarScreen.tsx:45 | — |
+```
+
+---
+
+## Sample Test Case Block (excerpt)
+
+```markdown
+### TC-052 — Aadhaar Number Validation
+
+**Type**: Validation
+**Related Story**: US-011
+**Related BRD**: BRD-019
+**Verdict**: FAIL
+**Confidence**: HIGH
+
+#### Test Steps vs Implementation
+
+| # | Test Step | Expected Outcome | Actual Implementation | Step Status |
+|---|-----------|-----------------|----------------------|-------------|
+| 1 | Navigate to Aadhaar verification screen | Screen visible | AadhaarScreen.tsx exists — renders correctly | PASS |
+| 2 | Enter 11-digit number (e.g., 12345678901) | Show error "Please enter valid 12-digit Aadhaar number" | No error shown — maxLength=12 allows 11 chars to pass | FAIL |
+| 3 | Enter alphabetic characters | Characters rejected | No regex filter — alphabetic input accepted | FAIL |
+| 4 | Enter valid 12-digit number | Field valid, no error | Accepted — no digit-only validation | PARTIAL |
+
+#### Evidence Files
+- `src/screens/kyc/AadhaarScreen.tsx:45` — aadhaarNumber TextInput with maxLength=12 only
+- `src/validation/kycSchema.ts:23` — kycSchema — aadhaarNumber: Yup.string().required() — no matches() or length check
+
+#### Verdict Reason
+Validation only checks required(). Does not enforce 12-digit minimum, 12-digit maximum, or digits-only.
+11-digit Aadhaar passes validation. Non-numeric characters are accepted.
+
+#### Recommendation
+In kycSchema.ts:23, update aadhaarNumber validation:
+  aadhaarNumber: Yup.string()
+    .required('Please enter valid 12-digit Aadhaar number')
+    .matches(/^\d{12}$/, 'Please enter valid 12-digit Aadhaar number')
+Add VALIDATION_REGEX.numericOnly to AadhaarScreen.tsx TextInput regex prop.
+```

package/.github/skills/code-test-coverage-analyzer/references/android-patterns.md

@@ -0,0 +1,229 @@
+# Android — Scanning Patterns Reference
+
+Load this file ONLY when the detected platform is Android (Kotlin/Java).
+
+---
+
+## Screen Detection Patterns
+
+**File patterns** (Glob):
+```
+**/*Activity.kt
+**/*Fragment.kt
+**/*Activity.java
+**/*Fragment.java
+**/*Screen.kt
+```
+
+**Confirmation**: Extends `AppCompatActivity`, `Fragment`, `DialogFragment`, or `BottomSheetDialogFragment`.
+
+**Layout files**:
+```
+**/res/layout/**/*.xml
+```
+
+---
+
+## State Management Detection
+
+| Library | Signal |
+|---|---|
+| ViewModel + LiveData | `androidx.lifecycle.ViewModel`, `LiveData`, `MutableLiveData` |
+| ViewModel + StateFlow | `StateFlow`, `MutableStateFlow`, `viewModelScope` |
+| MVI | `Intent` sealed classes, `State` sealed classes, `Effect` |
+
+---
+
+## API Call Patterns
+
+**HTTP client detection**: `okhttp3` or `retrofit2` in `build.gradle`.
+
+**Grep patterns**:
+```
+@GET\(
+@POST\(
+@PUT\(
+@PATCH\(
+@DELETE\(
+OkHttpClient
+\.newCall\(
+Retrofit\.Builder
+enqueue\(
+okhttp3
+retrofit2
+```
+
+**Repository / Data source files**:
+```
+**/*Repository.kt
+**/*DataSource.kt
+**/*RemoteDataSource.kt
+**/*ApiService.kt
+```
+
+**Interceptor files**:
+```
+**/*Interceptor.kt
+**/*Interceptor.java
+```
+
+---
+
+## Validation Patterns
+
+**Grep patterns**:
+```
+\.isEmpty\(\)
+\.isBlank\(\)
+\.length <
+\.length >
+TextUtils\.isEmpty
+Patterns\.EMAIL_ADDRESS
+\.matches\(
+binding\..*setError\(
+textInputLayout\.error =
+```
+
+**String resource files** (MUST resolve string IDs to actual strings):
+```
+**/res/values/strings.xml
+**/res/values-*/strings.xml
+```
+
+---
+
+## Navigation Patterns
+
+**Library detection**: `navigation-fragment-ktx` in build.gradle → Navigation Component.
+
+**Grep patterns**:
+```
+findNavController\(\)
+navController\.navigate\(
+startActivity\(Intent\(
+Intent\(this,
+startActivityForResult\(
+popBackStack\(\)
+Navigation\.findNavController
+```
+
+**NavGraph files**:
+```
+**/res/navigation/**/*.xml
+```
+
+---
+
+## Business Logic Patterns
+
+**File patterns**:
+```
+**/*ViewModel.kt
+**/*UseCase.kt
+**/*Interactor.kt
+**/*Service.kt
+**/*Manager.kt
+**/domain/**/*.kt
+```
+
+**Grep patterns**:
+```
+if.*eligible
+if.*approved
+if.*limit
+Math\.round\(
+Math\.floor\(
+Math\.ceil\(
+.toBigDecimal\(\)
+calculateAmount
+calculateInterest
+BigDecimal\(
+```
+
+---
+
+## UI Element Patterns
+
+**Grep patterns (XML layouts)**:
+```
+<EditText
+<TextInputEditText
+<TextInputLayout
+<Button
+<MaterialButton
+<TextView
+<Spinner
+<RecyclerView
+<ProgressBar
+<CircularProgressIndicator
+hint=
+```
+
+**Grep patterns (Kotlin code)**:
+```
+binding\..*\.text =
+binding\..*\.setError\(
+Snackbar\.make\(
+Toast\.makeText\(
+AlertDialog\.Builder\(
+BottomSheetDialog\(
+```
+
+---
+
+## Localization Patterns
+
+**String resources**:
+```
+**/res/values/strings.xml
+**/res/values-en/strings.xml
+```
+
+**Grep patterns**:
+```
+getString\(R\.string\.
+resources\.getString\(
+context\.getString\(
+```
+
+---
+
+## Error Handling Patterns
+
+**Grep patterns**:
+```
+catch\s*\(
+HttpException
+IOException
+SocketTimeoutException
+onFailure\(
+\.onError\{
+Timber\.e\(
+Log\.e\(
+```
+
+---
+
+## Authentication Patterns
+
+**Grep patterns**:
+```
+EncryptedSharedPreferences.*token
+SharedPreferences.*token
+Authorization.*Bearer
+accessToken
+refreshToken
+Authenticator
+```
+
+---
+
+## Feature Flag Patterns
+
+**Grep patterns**:
+```
+RemoteConfig
+featureFlag
+isEnabled\(
+BuildConfig\.
+```