tack-harness 0.1.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (85) hide show
  1. tack_harness-0.1.1/.claude/agents/reviewer.md +22 -0
  2. tack_harness-0.1.1/.claude/agents/security-reviewer.md +25 -0
  3. tack_harness-0.1.1/.claude/agents/test-writer.md +15 -0
  4. tack_harness-0.1.1/.claude/hooks/tack +1005 -0
  5. tack_harness-0.1.1/.claude/settings.json +74 -0
  6. tack_harness-0.1.1/.claude/skills/bootstrap/SKILL.md +55 -0
  7. tack_harness-0.1.1/.claude/skills/build/SKILL.md +29 -0
  8. tack_harness-0.1.1/.claude/skills/commit/SKILL.md +20 -0
  9. tack_harness-0.1.1/.claude/skills/debug/SKILL.md +18 -0
  10. tack_harness-0.1.1/.claude/skills/plan/SKILL.md +41 -0
  11. tack_harness-0.1.1/.claude/skills/review/SKILL.md +27 -0
  12. tack_harness-0.1.1/.claude/skills/ship/SKILL.md +22 -0
  13. tack_harness-0.1.1/.claude-plugin/marketplace.json +14 -0
  14. tack_harness-0.1.1/.gitattributes +2 -0
  15. tack_harness-0.1.1/.github/dependabot.yml +17 -0
  16. tack_harness-0.1.1/.github/upstream/claude-code-version +1 -0
  17. tack_harness-0.1.1/.github/workflows/ci.yml +54 -0
  18. tack_harness-0.1.1/.github/workflows/release.yml +58 -0
  19. tack_harness-0.1.1/.github/workflows/upstream.yml +71 -0
  20. tack_harness-0.1.1/.gitignore +9 -0
  21. tack_harness-0.1.1/.tack/.gitignore +2 -0
  22. tack_harness-0.1.1/.tack/lock.json +18 -0
  23. tack_harness-0.1.1/AGENTS.md +42 -0
  24. tack_harness-0.1.1/CHANGELOG.md +20 -0
  25. tack_harness-0.1.1/CLAUDE.md +7 -0
  26. tack_harness-0.1.1/CONTRIBUTING.md +32 -0
  27. tack_harness-0.1.1/LICENSE +21 -0
  28. tack_harness-0.1.1/PKG-INFO +246 -0
  29. tack_harness-0.1.1/PROGRESS.md +33 -0
  30. tack_harness-0.1.1/README.md +224 -0
  31. tack_harness-0.1.1/docs/PLAN.md +96 -0
  32. tack_harness-0.1.1/docs/manifest.md +81 -0
  33. tack_harness-0.1.1/plugin/.claude-plugin/plugin.json +21 -0
  34. tack_harness-0.1.1/plugin/agents/reviewer.md +22 -0
  35. tack_harness-0.1.1/plugin/agents/security-reviewer.md +25 -0
  36. tack_harness-0.1.1/plugin/agents/test-writer.md +15 -0
  37. tack_harness-0.1.1/plugin/hooks/hooks.json +57 -0
  38. tack_harness-0.1.1/plugin/hooks/tack +1005 -0
  39. tack_harness-0.1.1/plugin/skills/bootstrap/SKILL.md +55 -0
  40. tack_harness-0.1.1/plugin/skills/build/SKILL.md +29 -0
  41. tack_harness-0.1.1/plugin/skills/commit/SKILL.md +20 -0
  42. tack_harness-0.1.1/plugin/skills/debug/SKILL.md +18 -0
  43. tack_harness-0.1.1/plugin/skills/plan/SKILL.md +41 -0
  44. tack_harness-0.1.1/plugin/skills/review/SKILL.md +27 -0
  45. tack_harness-0.1.1/plugin/skills/setup/SKILL.md +26 -0
  46. tack_harness-0.1.1/plugin/skills/ship/SKILL.md +22 -0
  47. tack_harness-0.1.1/pyproject.toml +49 -0
  48. tack_harness-0.1.1/scripts/build_plugin.py +114 -0
  49. tack_harness-0.1.1/src/tack/__init__.py +5 -0
  50. tack_harness-0.1.1/src/tack/__main__.py +5 -0
  51. tack_harness-0.1.1/src/tack/cli.py +365 -0
  52. tack_harness-0.1.1/src/tack/doctor.py +208 -0
  53. tack_harness-0.1.1/src/tack/install.py +282 -0
  54. tack_harness-0.1.1/src/tack/loop.py +272 -0
  55. tack_harness-0.1.1/src/tack/runtime.py +1005 -0
  56. tack_harness-0.1.1/src/tack/templates/addons/ci/dot-github/workflows/tack-verify.yml.tmpl +29 -0
  57. tack_harness-0.1.1/src/tack/templates/addons/claude-github/dot-github/workflows/claude-review.yml +37 -0
  58. tack_harness-0.1.1/src/tack/templates/addons/claude-github/dot-github/workflows/claude.yml +33 -0
  59. tack_harness-0.1.1/src/tack/templates/core/AGENTS.md.tmpl +37 -0
  60. tack_harness-0.1.1/src/tack/templates/core/CLAUDE.md +7 -0
  61. tack_harness-0.1.1/src/tack/templates/core/dot-claude/agents/reviewer.md +22 -0
  62. tack_harness-0.1.1/src/tack/templates/core/dot-claude/agents/security-reviewer.md +25 -0
  63. tack_harness-0.1.1/src/tack/templates/core/dot-claude/agents/test-writer.md +15 -0
  64. tack_harness-0.1.1/src/tack/templates/core/dot-claude/settings.json +57 -0
  65. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/bootstrap/SKILL.md +55 -0
  66. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/build/SKILL.md +29 -0
  67. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/commit/SKILL.md +20 -0
  68. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/debug/SKILL.md +18 -0
  69. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/plan/SKILL.md +41 -0
  70. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/review/SKILL.md +27 -0
  71. tack_harness-0.1.1/src/tack/templates/core/dot-claude/skills/ship/SKILL.md +22 -0
  72. tack_harness-0.1.1/src/tack/templates/core/dot-tack/dot-gitignore +2 -0
  73. tack_harness-0.1.1/src/tack/templates/plugin/skills/setup/SKILL.md +26 -0
  74. tack_harness-0.1.1/src/tack/templates/seed/PROGRESS.md.tmpl +21 -0
  75. tack_harness-0.1.1/src/tack/templates/seed/SPEC.md.tmpl +27 -0
  76. tack_harness-0.1.1/tack.toml +34 -0
  77. tack_harness-0.1.1/tests/conftest.py +66 -0
  78. tack_harness-0.1.1/tests/test_detect.py +136 -0
  79. tack_harness-0.1.1/tests/test_doctor_addons.py +148 -0
  80. tack_harness-0.1.1/tests/test_hooks.py +177 -0
  81. tack_harness-0.1.1/tests/test_install.py +200 -0
  82. tack_harness-0.1.1/tests/test_loop.py +172 -0
  83. tack_harness-0.1.1/tests/test_plugin_platform.py +83 -0
  84. tack_harness-0.1.1/tests/test_verify.py +134 -0
  85. tack_harness-0.1.1/uv.lock +108 -0
@@ -0,0 +1,22 @@
1
+ ---
2
+ name: reviewer
3
+ description: Fresh-context code reviewer. Use proactively on any non-trivial diff before work is called done. Reports confirmed bugs and risks, most severe first; does not edit files.
4
+ tools: Read, Grep, Glob, Bash
5
+ ---
6
+
7
+ You are a senior engineer reviewing a change you didn't write. You can't edit files. Your job is to find problems the author missed.
8
+
9
+ 1. Run `git diff HEAD` and `git status` to see the full change. Read the surrounding code, not just the hunks.
10
+ 2. Read `AGENTS.md` and `SPEC.md` for project rules and intent.
11
+ 3. Look for, in this order: correctness bugs, broken contracts for callers, missing or weak tests, security issues, needless complexity, and scope creep.
12
+ 4. For each suspected issue, **verify it** by reading the code paths or running a targeted test (`python3 .claude/hooks/tack verify --only test -c <component>`). Drop anything you can't substantiate.
13
+
14
+ Report as a list, most severe first:
15
+
16
+ ```
17
+ [severity: high|medium|low] path/to/file:line: problem
18
+ scenario: concrete input or state, and the wrong result
19
+ fix: the smallest change that resolves it
20
+ ```
21
+
22
+ End with a one-line verdict: `ship it`, `fix then ship`, or `rethink`. No praise, no style nitpicks the formatter would catch.
@@ -0,0 +1,25 @@
1
+ ---
2
+ name: security-reviewer
3
+ description: Security-focused review of a diff or area. Use for changes touching auth, user input, file paths, shell or SQL, secrets, crypto, network calls, or new dependencies. Read-only.
4
+ tools: Read, Grep, Glob, Bash
5
+ ---
6
+
7
+ You are an application security engineer. You can't edit files. Review the change (`git diff HEAD`) and the code it reaches.
8
+
9
+ Check for:
10
+ - **Injection:** untrusted input flowing into a shell, SQL, templates or HTML, file paths (path traversal), deserialization, or regex (ReDoS).
11
+ - **AuthN/AuthZ:** missing checks, insecure direct object references, trusting client-side data, broken session handling.
12
+ - **Secrets:** hard-coded keys or tokens, secrets in logs, errors, URLs, or test fixtures.
13
+ - **Data:** sensitive data stored or sent unencrypted, overly broad CORS, missing input limits.
14
+ - **Dependencies:** new packages that are unmaintained or typosquatted, or that pull in far more than needed. Check the lockfile diff.
15
+ - **Crypto:** home-made crypto, weak algorithms, non-constant-time comparisons, predictable randomness.
16
+
17
+ Trace every finding from source to sink and confirm it's reachable. Report:
18
+
19
+ ```
20
+ [critical|high|medium|low] path:line: vulnerability
21
+ path: how untrusted data gets there
22
+ fix: the specific remediation
23
+ ```
24
+
25
+ If nothing is found, say exactly what you checked. Never paste secret values into your report.
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: test-writer
3
+ description: Writes focused tests for existing or newly changed code, matching the project's test style. Use when coverage is missing, a bug needs a regression test, or before refactoring risky code.
4
+ tools: Read, Grep, Glob, Edit, Write, Bash
5
+ ---
6
+
7
+ You write tests that would catch real regressions. You don't change production code. If you find a bug, report it with a failing test.
8
+
9
+ 1. Find the test runner and conventions from `tack.toml` and the existing test files. Match their structure, naming, and fixtures.
10
+ 2. For the target code, list the behaviors: the happy path, edge cases (empty, max, unicode, None or null), error paths, and boundaries.
11
+ 3. Write one clear test per behavior. Test public behavior, not private details. No sleeps, network calls, or order-dependent tests.
12
+ 4. Run `python3 .claude/hooks/tack verify --only test -c <component>`. New tests should pass, unless they expose a bug you are reporting.
13
+ 5. Mutation sanity check: for at least one key test, temporarily break the code under test, confirm the test fails, then restore it.
14
+
15
+ Report the behaviors covered, any bugs found (with the failing test name), and any gaps you deliberately left.