ki-engineering

Audit TypeScript/Bun repositories for Knowledge Islands engineering standards compliance.

Updated May 29, 2026
One-click install
npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ki-engineering
Source: https://github.com/knowledgeislands/ki-agentic-harness/tree/main/skills/ki-engineering
Command: npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your TypeScript/Bun repository adheres to the Knowledge Islands engineering standards, maintaining consistency across your toolchain and scripts.

Core Features & Use Cases

  • Engineering Standard Enforcement: Audits and enforces the common toolchain, script families, and configuration standards across Knowledge Islands repositories.
  • Build/Lint/Test Layer Ownership: Manages the shared build/lint/test layer required for TypeScript/Bun repositories in Knowledge Islands.
  • Package.json and Toolchain Pinning: Ensures proper package.json configuration and toolchain pinning with mise.toml.
  • CI Workflow Integration: Integrates with CI workflows for automated checks.
  • Use Case: When you want to ensure that your TypeScript/Bun repository meets the engineering standards of Knowledge Islands, use this skill to conduct audits and enforce the necessary configurations.

Quick Start

Run the ki-engineering:audit <repo> command to audit the engineering standards in the specified repository.

Frequently Asked Questions about ki-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit engineering standards in a TypeScript Bun repository?

To audit engineering standards in a TypeScript Bun repository, run the `ki-engineering:audit <repo>` command. This audits package.json metadata, script families, and toolchain configurations to ensure conformance with established guidelines.

What files are required to enforce toolchain consistency and configuration audits?

Enforcing toolchain consistency requires a `.ki-config.toml` file and a `package.json` for auditing configurations. Repository-specific CI integration also requires access to the `.github/workflows/ci.yml` file.

How do I pin my TypeScript toolchain configuration using mise.toml?

Pinning your TypeScript toolchain involves enforcing proper package.json configuration alongside toolchain pinning with mise.toml. This ensures build, lint, and test layers remain consistent across repositories.

Can I use this to integrate engineering standard checks into my CI workflows?

Yes, you can integrate engineering standard checks into CI workflows. The auditing process uses the repository's `.github/workflows/ci.yml` file to apply automated checks for toolchain and package metadata conformance.

Why does my package.json metadata fail the TypeScript repository conformance audit?

Your package.json metadata fails the conformance audit when it lacks required script families or proper toolchain configurations. The audit checks these elements against shared build, lint, and test layer standards to pinpoint inconsistencies.