Agent skill

Test Kanban Md

by antopolskiy in antopolskiy/kanban-md

Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks.

MITAuto-check passedProductivity & Automation

Install Test Kanban Md

skills CLI
$ npx skills add antopolskiy/kanban-md --skill test-kanban-md -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install antopolskiy/kanban-md test-kanban-md --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/antopolskiy/kanban-md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-kanban-md .claude/skills/test-kanban-md && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-kanban-md
GitHub stars
223
Token cost
~737 tokens
SKILL.md length
317 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks.

  • Works in 8 steps: Identify the affected package or… → Add the narrowest test that reproduces… → Run that test and confirm the pre-fix… → …
  • Reviewing a change
  • SKILL.md covers Required discipline, Bug-fix loop and Common verification commands
  • Calls go and make

What it does

Test Kanban Md is an agent skill from antopolskiy/kanban-md. Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks. Use when implementing or reviewing a change, fixing a bug, adding tests, updating snapshots, or deciding what evidence is required. Do not use as the source of release or schema-migration policy.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/test-patterns.md`).

It sits in Productivity & Automation, covering Task management, Debugging and Test-driven development. The repository describes itself as: File-based kanban board for autonomous agentic loop. CLI and TUI for multi-agent workflows. Skills included. The licence is MIT.

When your agent uses it

  • Reviewing a change
  • Updating snapshots
  • Deciding what evidence is required

Example prompts

  • “/test-kanban-md”

Requirements

  • Pre-approved tools (allowed-tools): Bash(go *), Bash(golangci-lint *), Bash(make *), Bash(git diff *)

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Identify the affected package or interface and study nearby test patterns.
  2. Add the narrowest test that reproduces the reported behavior.
  3. Run that test and confirm the pre-fix failure is meaningful.
  4. Implement the smallest sufficient fix.
  5. Run the reproducer again and confirm it passes.
  6. Run the affected package or E2E suite.
  7. Run the full repository tests and lint.
  8. Review snapshots, generated files, and the final diff for unintended changes.

What it can do on your machine

Read from SKILL.md and the folder at commit e3816f2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(go *)
    • Bash(golangci-lint *)
    • Bash(make *)
    • Bash(git diff *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Kanban Md loads about 737 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 317 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~737
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from antopolskiy/kanban-md at commit e3816f2, republished under its MIT licence (© antopolskiy). 317 words, ~737 tokens.

Download SKILL.mdSave it as .claude/skills/test-kanban-md/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
test-kanban-md
description
Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks. Use when implementing or reviewing a change, fixing a bug, adding tests, updating snapshots, or deciding what evidence is required. Do not use as the source of release or schema-migration policy.
allowed-tools
Bash(go *), Bash(golangci-lint *), Bash(make *), Bash(git diff *)

Test kanban-md

Choose the smallest fast feedback loop while developing, then widen verification in proportion to the change before declaring it complete.

Required discipline

  • Fix bugs with test-driven development: first reproduce the exact failure in a test and confirm it fails for the expected reason, then implement the fix.
  • Match the test layer to the behavior. Prefer package tests for internal logic, command tests for CLI wiring, E2E tests for complete binary workflows, and TUI behavioral or snapshot tests for rendered interaction.
  • Run focused tests during implementation, the affected package suite after the change, and the full suite before completing production-code work.
  • Run lint after Go changes and resolve findings introduced by the change.
  • Update golden files only after confirming the new rendering is intended, then inspect the resulting diff rather than accepting it blindly.
  • Report the exact commands run and distinguish passing checks, known baseline failures, and checks that were not run.

Bug-fix loop

  1. Identify the affected package or interface and study nearby test patterns.
  2. Add the narrowest test that reproduces the reported behavior.
  3. Run that test and confirm the pre-fix failure is meaningful.
  4. Implement the smallest sufficient fix.
  5. Run the reproducer again and confirm it passes.
  6. Run the affected package or E2E suite.
  7. Run the full repository tests and lint.
  8. Review snapshots, generated files, and the final diff for unintended changes.

Do not weaken an assertion merely to make a failing test pass. If the expected behavior is unclear, resolve that product decision before encoding it.

Common verification commands

bash
# One test or package during development
go test ./path/to/package -run TestName -count=1
go test ./path/to/package -count=1

# Repository-wide checks
go test ./...
golangci-lint run ./...

# Full branch validation used by the repository
make precommit

Use make precommit before integration when the change warrants the full build, race-enabled coverage, E2E, lint, and clean-worktree checks. If it fails because of a pre-existing baseline, verify the current diff separately and report the baseline precisely; do not silently present a partial check as a full pass.

For package locations, helpers, and TUI snapshot commands, read references/test-patterns.md.

© antopolskiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/test-kanban-md of antopolskiy/kanban-md.

  • SKILL.md
  • references/test-patterns.md

Open the folder on GitHubat commit e3816f2

Compare with similar skills

Test Kanban Md next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Kanban Md compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Kanban Md this skillantopolskiy/kanban-md223—~737Automated safety check: PassMIT
Issue Trackingstatic-web-server/static-web-server2.4k—~1.5kAutomated safety check: PassApache-2.0
Tbdjlevy/strif131—~3.5kAutomated safety check: PassMIT
Compound Engineering DebugEveryInc/compound-engineering-plugin25k—~4.2kAutomated safety check: PassMIT
Ship Fixantonio-orionus/Arroxy397—~1.8kAutomated safety check: PassMIT
Foreman DebugVisionForge-OU/foreman443—~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Issue Tracking

    static-web-server/static-web-server

    Triage, reproduce, debug, and fix issues in the Static Web Server (SWS) project — bug reports, regressions, root-cause analysis, minimal fixes with regression tests, v2 backports, and security…

    2.4k GitHub stars~1.5k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Tbd

    jlevy/strif

    Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents.

    131 GitHub stars~3.5k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Compound Engineering Debug

    EveryInc/compound-engineering-plugin

    Finds the root cause of failing or slow behavior with a hypothesis-driven loop, then fixes it test-first if you choose, or hands back a diagnosis only.

    25k GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Ship Fix

    antonio-orionus/Arroxy

    End-to-end Arroxy flow for taking a bug fix (or small feature) from report to published release - worktree, test-first fix, PR, CodeRabbit, CI validation, squash-merge, version bump and tag.

    397 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Foreman Debug

    VisionForge-OU/foreman

    Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.

    443 GitHub stars~1.1k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Fix Bug

    tddworks/ClaudeBar

    Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design.

    1.5k GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed

More from antopolskiy/kanban-md

  • Kanban Md

    antopolskiy/kanban-md

    Manage project tasks using kanban-md, a file-based kanban board CLI.

    223 GitHub stars~4k tokensUpdated 5 days ago
    Auto-check passed
  • Release Kanban Md

    antopolskiy/kanban-md

    Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.

    223 GitHub stars~1.2k tokensUpdated 5 days ago
    Auto-check passed
  • Evolve Kanban Md Formats

    antopolskiy/kanban-md

    Evolve kanban-md config.yml schemas and task Markdown frontmatter without breaking existing boards.

    223 GitHub stars~795 tokensUpdated 5 days ago
    Auto-check passed
  • Kanban Based Development

    antopolskiy/kanban-md

    Autonomous, parallel-safe development workflow using kanban-md.

    223 GitHub stars~2.3k tokensUpdated 5 days ago
    Auto-check passed
  • Design Kanban Md Output

    antopolskiy/kanban-md

    Preserve and evolve kanban-md table, compact, and JSON output contracts.

    223 GitHub stars~767 tokensUpdated 5 days ago
    Auto-check passed
  • Kanban Md Principal Owner

    antopolskiy/kanban-md

    Review kanban-md feature requests, issues, PRs, and design proposals for product fit, domain-model growth, configurability, and compatibility.

    223 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed

Questions about Test Kanban Md

What does Test Kanban Md do?

Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks. Test Kanban Md is an agent skill from antopolskiy/kanban-md. Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks.

When should I use Test Kanban Md?

Test Kanban Md fits situations like: reviewing a change; updating snapshots; deciding what evidence is required.

How do I install Test Kanban Md in Claude Code?

Run `npx skills add antopolskiy/kanban-md --skill test-kanban-md -a claude-code`. Or copy the skill folder (.agents/skills/test-kanban-md in antopolskiy/kanban-md) into .claude/skills/test-kanban-md in your project. Claude Code loads it when a task matches its description.

How do I install Test Kanban Md in Codex?

Run `npx skills add antopolskiy/kanban-md --skill test-kanban-md -a codex`. Or copy the skill folder (.agents/skills/test-kanban-md in antopolskiy/kanban-md) into .agents/skills/test-kanban-md in your project. Codex loads it when a task matches its description.

Can I use Test Kanban Md in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add antopolskiy/kanban-md --skill test-kanban-md -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-kanban-md, .gemini/skills/test-kanban-md, .github/skills/test-kanban-md and .opencode/skills/test-kanban-md in your project.

What does Test Kanban Md need to run?

Going by SKILL.md and its folder, Test Kanban Md needs the command-line tools its instructions call (go and make). Its frontmatter pre-approves these tools: Bash(go *), Bash(golangci-lint *), Bash(make *), Bash(git diff *).

Does Test Kanban Md access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Kanban Md safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Kanban Md use?

Test Kanban Md is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Kanban Md use?

About 737 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 491 tokens, read only when the agent opens those files.

What are the alternatives to Test Kanban Md?

Skills that share tags, products or a category with Test Kanban Md: Issue Tracking (static-web-server/static-web-server, 2.4k stars), Tbd (jlevy/strif, 131 stars), Compound Engineering Debug (EveryInc/compound-engineering-plugin, 25k stars) and Ship Fix (antonio-orionus/Arroxy, 397 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Kanban Md?

antopolskiy (a GitHub user) maintains it in antopolskiy/kanban-md, which has 223 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: antopolskiy/kanban-md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.