agentleFS
ric03uecric03uec/clawrium/.claude/skills/itx-verify/SKILL.md

itx-verify

Skill67 starsChanged 2 months agoApache-2.0View on GitHub

Run tests, lint, and validate current changes

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run all verification checks to ensure code quality.

    line 9
  2. Distinctive:

    All tests must pass

    line 31
  3. Distinctive:

    All lint checks must pass

    line 38
  4. Distinctive:

    Ensure critical paths are tested

    line 46
  5. Distinctive:

    Must pass before creating PRs

    line 94
  6. Distinctive:

    Use this after making changes, before committing

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verification

Run all verification checks to ensure code quality.

Instructions

  1. Load Configuration:
    ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json"
    if [ -f "$ITX_CONFIG" ]; then
      TEST_CMD=$(jq -r '.build.test_command // "make test"' "$ITX_CONFIG")
      LINT_CMD=$(jq -r '.build.lint_command // "make lint"' "$ITX_CONFIG")
      COV_CMD=$(jq -r '.build.coverage_command // "make test-cov"' "$ITX_CONFIG")
    else
      TEST_CMD="make test"
      LINT_CMD="make lint"
      COV_CMD="make test-cov"
    fi
  2. Run Tests:
    $TEST_CMD
    • All tests must pass
    • Note any failures with details
  3. Run Linter:
    $LINT_CMD
    • All lint checks must pass
    • Fix any issues found
  4. Check Coverage (optional):
    $COV_CMD
    • Review coverage for new code
    • Ensure critical paths are tested
  5. Report Results:
    ## Verification Results
    
    ### Tests
    - Command: <test command>
    - Status: PASS/FAIL
    - Details: <summary>
    
    ### Lint
    - Command: <lint command>
    - Status: PASS/FAIL
    - Details: <summary>
    
    ### Coverage
    - Status: <percentage>
    - New code coverage: <assessment>
  6. If Failures:
    • Fix issues
    • Re-run verification
    • Iterate until all checks pass

Configuration

Customize build commands in .claude/itx-config.json:

{
  "build": {
    "test_command": "npm test",
    "lint_command": "npm run lint",
    "coverage_command": "npm run test:coverage"
  }
}

Defaults (no config):

  • test_command: make test
  • lint_command: make lint
  • coverage_command: make test-cov

Notes

  • This is a local operation
  • Must pass before creating PRs
  • Use this after making changes, before committing
  • Can be run multiple times during development

Prompt Logging

REQUIRED: Append prompt log to .itx/<N>/02_VERIFY.md.

See AGENTS.md for format specification.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.