[WIP] Create lint quality campaign 2026

[Copilot]

• Create campaign specification file at .github/workflows/lint-quality-2026.campaign.md
• Compile the campaign using gh aw campaign commands
• Review compiled output and verify campaign structure
• Commit campaign specification file
• Verify the campaign validates successfully

Campaign Details:

• ID: lint-quality-2026
• State: active
• Risk Level: low
• Workflows: super-linter, tidy, static-analysis-report
• Project Board: TBD (will be created by safe-outputs handler job)

The campaign specification has been created and validated successfully. All three workflows (super-linter, tidy, static-analysis-report) are recognized and compiled. The project board URL placeholder is set to be updated after the safe-outputs job creates it.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Lint Quality Campaign 2026</issue_title>
<issue_description>> Original Request

I want to create a lint campaign

---

🎯 Campaign Details

Campaign ID: lint-quality-2026
Campaign Name: Lint Quality Campaign 2026
Project Board: TBD (will be created by safe-outputs job)
Risk Level: Low
State: Planned

📋 Workflows

Existing Workflows (Ready to Use)

• super-linter: Markdown quality checks using Super Linter, creates issues for violations
• tidy: Automatically formats and tidies code files (Go, JS, TypeScript)
• static-analysis-report: Security scanning with zizmor, poutine, and actionlint

🎯 Goals

• Maintain consistent code formatting across Go, JavaScript, and TypeScript files
• Identify and fix linting issues proactively before they reach production
• Detect security vulnerabilities early through static analysis
• Ensure Markdown documentation quality
• Reduce technical debt through automated code quality checks

⏱️ Timeline

• Start Date: 2026-01-14
• Target Completion: Ongoing (continuous quality maintenance)

---

🤖 Instructions for Copilot Coding Agent

The campaign specification file has been created at .github/workflows/lint-quality-2026.campaign.md.

Your task:

1. Run gh aw compile lint-quality-2026 to compile the campaign
2. Review the compiled output and ensure all workflows are properly configured
3. Commit the campaign specification file and any generated files
4. Create a pull request with your changes

Note: The project board will be created by the safe-outputs handler job. After the PR is merged, the project board URL will be available and should be updated in the campaign specification file.</issue_description>

Comments on the Issue (you are @copilot in this section)

@mnkiefer ✅ **Campaign Specification Created!**

I've generated the lint quality campaign specification and prepared it for compilation.

📊 Project Board: Being created by safe-outputs handler

• Custom fields will include: Worker/Workflow, Priority, Status, Start Date, End Date, Effort
• Views will include: Campaign Roadmap (timeline), Task Tracker (table), Progress Board (kanban)

📁 File Created:

• .github/workflows/lint-quality-2026.campaign.md

📝 Workflows Included:

1. super-linter - Markdown quality checks (weekday schedule)
2. tidy - Code formatting and linting for Go, JS, TS (daily + on push)
3. static-analysis-report - Security scanning with zizmor, poutine, actionlint (daily)

🎯 Campaign Goals:

• Maintain consistent code formatting
• Proactively identify and fix linting issues
• Detect security vulnerabilities early
• Ensure documentation quality
• Reduce technical debt

Next Steps:
The Copilot Coding Agent will now:

1. Compile the campaign using gh aw compile lint-quality-2026
2. Create a pull request with the compiled files

The project board will be created automatically and its URL will be available after the safe-outputs job completes.

AI generated by Campaign Generator</comment_new>

• Fixes githubnext/gh-aw#9904

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.