dev-checker

The dev-checker skill is an essential development utility designed for the Medellin Spark platform to ensure code stability and maintainability. It provides an automated, systematic approach to verifying the integrity of a codebase before any git commit or deployment action. By centralizing common development health checks, this skill reduces the likelihood of shipping broken builds, type errors, or sensitive information. It acts as an automated quality gate for developers who want to maintain high standards throughout their iteration cycle.

• Performs static type analysis using pnpm tsc --noEmit to identify type-related regressions without triggering build artifacts.

• Executes build validation via pnpm build to ensure the application compiles correctly within strict timing constraints.

• Enforces coding standards and style consistency by running pnpm lint to automatically identify and flag potential issues.

• Maintains a dedicated pre-commit checklist that includes verifying the absence of console.log statements, ensuring API keys are not accidentally included in source files, and verifying that environment files are not staged for version control.

• Provides a robust pre-deploy validation suite that checks if tests pass, verifies the status of Edge Functions, ensures all environment variables are correctly set, and confirms that database migrations have been successfully applied.

• Offers built-in troubleshooting patterns for common TypeScript errors and build failures, including commands to clear the Vite cache and rebuild dependencies effectively.

• Intended for use by software engineers and developers working on Vite, TypeScript, React, shadcn-ui, or Tailwind CSS stacks.

• Inputs typically involve a direct request to validate the current branch or directory state, such as 'Run dev checks' or 'Check if ready to commit'.

• Outputs are structured as pass/fail summaries based on the checklists provided, helping the user quickly determine if they are safe to proceed with Git operations.

• Constraints include requiring Node.js, npm/pnpm, and the standard project configuration to function correctly. Developers should ensure the local environment is pre-configured according to the repository standards before initiating the checker.