ki-repo

Audits Git repos for Knowledge Islands compliance across files, GitHub settings, and deeper configurations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that a Knowledge Islands compliant git repo adheres to the established standards, covering local files, GitHub settings, and deeper GitHub configurations.

Core Features & Use Cases

  • Local Files Compliance: Checks for the presence of required files like README.md, LICENSE, .gitignore, and .ki-config.toml.
  • GitHub Settings Compliance: Validates GitHub settings such as default branch, license, merge policy, visibility, and security features.
  • Deeper GitHub Compliance: Ensures deeper GitHub configurations like Dependabot alerts, secret scanning, and push protection are correctly set up.
  • Use Case: When onboarding a new repo or auditing existing repos for compliance with the Knowledge Islands standards.

Quick Start

Run ki:repo:audit . to check the compliance of the current directory.

Frequently Asked Questions about ki-repo

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

FAQPage Schema
How do I audit a git repo for compliance and standard adherence?

To audit a git repo for compliance, run the command `ki:repo:audit .` in the target directory. This checks local files like `README.md` and `LICENSE`, GitHub settings, and deeper configurations like Dependabot alerts against established standards.

What GitHub settings are checked during a repo configuration audit?

A repo configuration audit validates GitHub settings including default branch, license, merge policy, visibility, and security features. It also verifies deeper configurations like Dependabot alerts, secret scanning, and push protection are correctly set up.

Do I need the gh CLI to check repo compliance and standard configurations?

Yes, you need the gh CLI installed with repo-admin scope to check repo compliance and standard configurations. The audit evaluates local files alongside GitHub settings and deeper repository configurations using this dependency.

What local files are required for Knowledge Islands repo compliance?

Knowledge Islands repo compliance requires specific local files including `README.md`, `LICENSE`, `.gitignore`, and `.ki-config.toml`. The audit process checks for the presence of these required files in the git repository.

Can I use this audit for source code linting and formatting?

No, this audit cannot be used for source code linting and formatting. It focuses strictly on configuration and governance, ensuring compliance with local files, GitHub settings, and deeper configurations rather than analyzing source code.

When should I run a repo compliance audit on my GitHub repositories?

You should run a repo compliance audit when onboarding a new repository or auditing existing repositories for compliance with Knowledge Islands standards. It ensures local files and GitHub configurations adhere to established governance rules.