Automation & Scripting Tools
Relevant source files
The following files were used as context for generating this wiki page:
Automation and scripting tools within the bl1nk platform provide a robust framework for CI/CD, project initialization, and spec-driven development. These tools facilitate enterprise-grade infrastructure by automating testing, multi-platform releases, and security scanning, while also providing interactive workflows for requirements gathering and task execution.
The scope of these tools extends from GitHub Actions workflows for production-ready deployments to localized bash and PowerShell scripts for managing the .specify/ and .kiro/ directories. This infrastructure ensures project health improvements by enforcing code quality standards and bilingual documentation parity through automated validation scripts.
Sources: specs/main/plan.md:9-16, Comprehensive.md:7-14
CI/CD Infrastructure & GitHub Actions
The platform utilizes a comprehensive suite of GitHub Actions to automate the software development lifecycle. This includes continuous integration (CI) for testing and building, as well as specialized workflows for desktop application releases and containerization.
Core Workflow Components
| Workflow | Purpose | Key Tools |
|---|---|---|
| CI Pipeline | Linting, type-checking, unit, and E2E testing | Vitest, Playwright, pnpm |
| Electron Release | Multi-platform builds (Win/Mac/Linux) with code signing | Electron Forge, Apple ID, DigiCert |
| Docker Build | Multi-platform container images (amd64, arm64) | Docker Buildx, GHCR |
| Security Scanning | Dependency and secret analysis | Snyk, CodeQL, SonarCloud |
| Database Checks | Prisma schema validation and migrations | Prisma CLI |
Sources: Comprehensive.md:19-35, specs/main/plan.md:165-224
CI Pipeline Flow
The CI pipeline is triggered on push and pull requests to main and develop branches. It follows a modular structure where tests and builds depend on a successful environment setup and linting.
The CI pipeline maintains a target execution time of under 15 minutes by utilizing aggressive caching for node_modules, pnpm-store, and Playwright browsers.
Sources: specs/main/plan.md:165-195, Comprehensive.md:112-132
Spec-Driven Development Tools
Automation is integrated into the development process through tools that manage "Spec-Kit" and "Kiro" workflows. These tools use structured directories and scripts to guide developers from initial requirements to task implementation.
Spec-Kit Workflow (specify-cli)
The Spec-Kit integration provides a 7-phase workflow: Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement. It relies on a set of bash scripts for directory initialization and state management.
- Initialization:
specify initsets up the.specify/directory. - Feature Creation:
.specify/scripts/bash/create-new-feature.shinitializes a new numbered feature branch (e.g.,001-feature-name). - Planning:
.specify/scripts/bash/setup-plan.shprepares the environment for creating technical strategy documents. - Analysis: Analysis involves cross-artifact consistency checks to ensure all requirements are covered by tasks.
Sources: plugins/spec-kit-skill/skills/spec-kit-skill/SKILL.md:5-24, plugins/spec-kit-skill/skills/spec-kit-skill/SKILL.md:275-300
Kiro Feature Orchestration
The Kiro workflow automates the transition between requirements gathering (EARS format) and task execution. It utilizes a state machine logic to ensure user approval before advancing phases.
Kiro focuses on absolute minimal code generation and test-driven increments, ensuring that no orphaned code is introduced into the project.
Sources: plugins/kiro-skill/skills/kiro-skill/SKILL.md:13-35, plugins/kiro-skill/skills/kiro-skill/SKILL.md:188-200
Autonomous Task Initialization
For long-running autonomous processes, the platform uses an Initializer Agent that sets up a standardized task-tracking environment. This tool ensures that multiple autonomous tasks can run concurrently without conflicts.
Automated Task Structure
The initializer creates two primary files in the .autonomous/<task-name>/ directory:
- task_list.md: A comprehensive breakdown of sub-tasks (10-100+ items depending on complexity).
- progress.md: A session-by-session log of accomplishments and issues.
# Example Task List Structure
## Meta
- Created: 2025-12-02
- Task Directory: .autonomous/my-task
- Total Tasks: 20
- Completed: 0/20 (0%)
## Tasks
### Phase 1: Foundation
- [ ] Task 1: [Actionable Description]
Sources: plugins/autonomous-skill/skills/autonomous-skill/templates/initializer-prompt.md:15-50, plugins/autonomous-skill/skills/autonomous-skill/templates/initializer-prompt.md:120-135
Scripting Utilities
The platform includes various localized scripts to support specific infrastructure goals, particularly in bilingual documentation and codebase reorganization.
| Script / Tool | Functionality |
|---|---|
mmdc (Mermaid CLI) | Generates SVG/PNG exports from Mermaid Markdown diagrams. |
markdown-link-check | Validates internal links and external references in documentation. |
pnpm run organize:agents | Automates the migration of 500+ agent files into categorized directories. |
act | Local runner for GitHub Actions workflows to test CI/CD pipelines before pushing. |
actionlint | Syntax validator for GitHub Actions YAML files. |
Sources: specs/main/plan.md:231-255, Comprehensive.md:165-175
Configuration & Environment Management
Automation tools rely on a standardized set of configuration files and GitHub Secrets to manage environments across development and production.
Required Secrets for Automation
The CI/CD platform requires high-privileged secrets for code signing and cloud integrations:
- macOS Signing:
APPLE_ID,APPLE_PASSWORD,APPLE_TEAM_ID. - Windows Signing:
WINDOWS_CERTIFICATE,WINDOWS_CERTIFICATE_PASSWORD. - Security/Testing:
SNYK_TOKEN,SONAR_TOKEN,CODECOV_TOKEN. - Container Registry:
GHCR_TOKEN.
Sources: Comprehensive.md:144-160, specs/main/plan.md:278-295
Development Environment Setup
Automation tools also enforce consistent workspace settings for developers via:
.eslintrc.json: Enforces strict TypeScript rules and preventsno-explicit-any..vscode/settings.json: Automates formatting on save using Prettier and ESLint..vscode/extensions.json: Recommends essential plugins for Prisma, Tailwind, and ESLint.
Sources: Comprehensive.md:183-210, specs/main/plan.md:105-115
Automation & Scripting Tools provide the structural backbone for the bl1nk-skill-platform. By combining rigorous GitHub Actions workflows for production with interactive scripting tools like Kiro and Spec-Kit for development, the project maintains high standards for reliability, security, and developer efficiency.