Nazar Report Skill

This skill generates a formatted report from scan results.

Workflow

Step 1: Check for Scan Results

Check if scan results exist in the conversation. If not, tell the user:

Once /nazar:scan ile tarama yapin, sonra /nazar:report ile rapor olusturabilirsiniz.

Step 2: Determine Format

Accept a format argument from the user. Supported formats:

• markdown (default) - Human-readable .md file
• html - Self-contained styled HTML file
• json - Machine-readable JSON for CI/CD pipelines

If no format specified, use markdown.

Step 3: Calculate Grade

Use this grading scale based on findings:

Step 4: Generate Report

Markdown Format (nazar-report.md)

# Nazar Security & Quality Report

**Project:** /path/to/project
**Frameworks:** React, Express, ...
**Scan Date:** YYYY-MM-DD HH:MM
**Grade:** A/B/C/D/F

---

## Summary

| Metric | Count |
|--------|-------|
| Total Issues | N |
| Critical | N |
| High | N |
| Medium | N |
| Low | N |

---

## Findings

| # | Severity | Location | Issue | Confidence | Suggested Fix |
|---|----------|----------|-------|------------|---------------|
| 1 | CRITICAL | src/db.js:15 | SQL Injection | High | Use parameterized queries |
| 2 | HIGH | src/auth.js:8 | Hardcoded Secret | High | Move to .env |
| ... | ... | ... | ... | ... | ... |

---

## Category Breakdown

### Security
- N issues found
- [list of security findings]

### Code Quality
- N issues found
- [list of quality findings]

### Dependencies
- N issues found
- [list of dependency findings]

### Platform Specific
- N issues found
- [list of platform findings]

---

## Recommendations

1. [Priority recommendation based on critical findings]
2. [Next priority recommendation]
3. ...

---

*Generated by Nazar - Security & Quality Scanner*

HTML Format (nazar-report.html)

Generate a self-contained HTML file with:

• Inline CSS using a dark theme (background: #1a1a2e, text: #e0e0e0, accent: #00d4aa)
• Color-coded severity badges:
  • Critical: #ff4757 (red)
  • High: #ff6b35 (orange)
  • Medium: #ffa502 (yellow)
  • Low: #2ed573 (green)
• Styled tables with alternating row colors
• Collapsible sections per category using HTML details/summary elements
• Grade displayed prominently with color coding (A=green, B=blue, C=yellow, D=orange, F=red)
• Responsive layout that works in any browser
• Same content structure as the markdown format
• Footer with "Generated by Nazar" and timestamp

JSON Format (nazar-report.json)

{
  "project": {
    "path": "/path/to/project",
    "frameworks": ["react", "express"],
    "scanDate": "2026-03-24T12:00:00Z"
  },
  "summary": {
    "grade": "B",
    "total": 12,
    "critical": 0,
    "high": 2,
    "medium": 5,
    "low": 5
  },
  "findings": [
    {
      "id": 1,
      "severity": "high",
      "category": "security",
      "type": "sql_injection",
      "file": "src/db.js",
      "line": 15,
      "description": "SQL query built with string concatenation",
      "confidence": "high",
      "fix": "Use parameterized queries"
    }
  ],
  "categories": {
    "security": { "count": 3, "findings": [1, 4, 7] },
    "quality": { "count": 5, "findings": [2, 3, 5, 8, 10] },
    "dependency": { "count": 2, "findings": [6, 9] },
    "platform": { "count": 2, "findings": [11, 12] }
  },
  "recommendations": [
    "Fix 2 high severity SQL injection issues in src/db.js",
    "Move hardcoded secrets to environment variables"
  ],
  "metadata": {
    "scanner": "nazar",
    "version": "1.0.0",
    "timestamp": "2026-03-24T12:00:00Z"
  }
}

Step 5: Write Report File

Write the generated report to the project root directory:

• Markdown: nazar-report.md
• HTML: nazar-report.html
• JSON: nazar-report.json

Step 6: Return Result

Tell the user:

• The file path where the report was saved
• The project grade
• A brief summary (total issues, critical count)

Example:

Rapor olusturuldu: /path/to/project/nazar-report.md Proje Notu: B (0 kritik, 2 yuksek, 5 orta, 5 dusuk)

Notes

• Reports should be self-contained -- no external dependencies for HTML, no references to external files
• The JSON format is designed for CI/CD consumption -- keep the schema stable and documented
• Always include the scan timestamp so reports can be compared over time
• If findings were fixed since the scan (via /nazar:fix), note which ones were resolved