chkcompliance
Check repository compliance with Brockhoff Cloud spec-driven development standards
What this skill does
# Check Repository Compliance
Validates that the current repository meets Brockhoff Cloud spec-driven development standards. Reports which components are compliant and which need attention.
## Usage
```
/bkff:chkcompliance
/bkff:chkcompliance --format=json
```
## Compliance Checks
The following components are validated:
### GitHub Configuration (.github/)
| Check | Path | Description |
|-------|------|-------------|
| github-dir | `.github/` | GitHub configuration directory |
| github-codeowners | `.github/CODEOWNERS` | Code review ownership rules |
| github-contributing | `.github/CONTRIBUTING.md` | Contribution guidelines |
| github-dependabot | `.github/dependabot.yml` | Automated dependency updates |
| github-pr-template | `.github/pull_request_template.md` | PR template for consistency |
| github-issue-templates | `.github/ISSUE_TEMPLATE/` | Issue templates directory |
| github-bug-template | `.github/ISSUE_TEMPLATE/bug_report.md` | Bug report template |
| github-feature-template | `.github/ISSUE_TEMPLATE/feature_request.md` | Feature request template |
### Agent Instructions
| Check | Path | Description |
|-------|------|-------------|
| agents-md | `AGENTS.md` | Agent instructions file with project overview |
| claude-md | `CLAUDE.md` | Must reference AGENTS.md |
| copilot-instructions | `.github/copilot-instructions.md` | Must reference AGENTS.md |
### Beads Issue Tracking
| Check | Path | Description |
|-------|------|-------------|
| beads-init | `.beads/` | Beads must be initialized |
| beads-health | `bd doctor` | Beads health check must pass |
## Output
### Human-Readable (default)
```
Compliance Report
─────────────────────────────────────
✓ github-dir
✓ github-codeowners
✗ github-contributing
→ File missing: .github/CONTRIBUTING.md
✓ agents-md
✓ claude-md
✓ beads-init
○ beads-health (skipped)
→ Beads not initialized
─────────────────────────────────────
2 check(s) failed (10 passed, 2 failed)
Run 'bkff:fixcompliance' to automatically fix issues
```
### JSON Format
```json
{
"timestamp": "2026-01-24T10:30:00Z",
"repository": "/path/to/repo",
"overall_status": "fail",
"checks_passed": 10,
"checks_failed": 2,
"checks_skipped": 1,
"checks_total": 13,
"checks": [
{
"name": "github-codeowners",
"path": ".github/CODEOWNERS",
"status": "pass",
"message": null,
"description": "Code review ownership rules",
"remediation": "Create CODEOWNERS with team ownership patterns"
}
]
}
```
## Requirements
- Must be run inside a git repository
- `jq` for JSON processing
- `bd` CLI for beads health check (optional - gracefully skips if not available)
## Exit Codes
- `0` - All checks passed
- `1` - One or more checks failed
- `2` - Not a git repository or other error
## Related Skills
- `/bkff:fixcompliance` - Automatically fix compliance issues
## Implementation
```bash
#!/usr/bin/env bash
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PLUGIN_DIR="$(dirname "$(dirname "$SCRIPT_DIR")")"
source "$PLUGIN_DIR/lib/common.sh"
source "$PLUGIN_DIR/lib/compliance.sh"
# Parse arguments
format="human"
for arg in "$@"; do
case "$arg" in
--format=json) format="json" ;;
--format=human) format="human" ;;
--json) format="json" ;;
esac
done
# Validate git repository
if ! is_git_worktree; then
error_exit "Not a git repository. This command must be run inside a git repository."
fi
# Run all compliance checks
report=$(run_all_checks)
# Output based on format
if [[ "$format" == "json" ]]; then
echo "$report"
else
echo "$report" | print_compliance_report
fi
# Exit with appropriate code
overall_status=$(echo "$report" | jq -r '.overall_status')
if [[ "$overall_status" == "pass" ]]; then
exit 0
else
exit 1
fi
```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.