Fullrun Skill

Overview

This skill implements a task execution system with the following features:

1. 1. State Management: Uses .claude-status.txt file to track execution state

- 0 = Idle, ready to execute (or file doesn't exist) - 1 = Claude is currently executing tasks - 2 = All tasks completed, monitoring should exit

1. 2. Task List: Reads pending tasks from INLINECODE4

1. 3. Scripts: Executable scripts in the scripts/ directory

Requirements

• - jq - Required for install/uninstall scripts

- macOS: brew install jq - Linux: apt install jq or INLINECODE8

File Structure

CODEBLOCK0

Usage

Installation (run once per project)

The installer creates project-local configuration in ./.claude/ - no global settings are modified.

CODEBLOCK1

What the installer does:

1. 1. Creates .claude/ directory in your project
2. Copies scripts to INLINECODE11
3. Creates or updates .claude/settings.local.json with:

- Permission rule for project scripts
- SessionStart hook for auto-monitoring

Scope: Configuration is project-local only. Other projects are not affected.

Uninstall

CODEBLOCK2

This removes:

• - The .claude/fullrun/ directory
• Fullrun permission rule from INLINECODE14
• Fullrun hook from SessionStart (preserves other hooks)
• INLINECODE15 if it becomes empty

Start scheduled monitoring (recommended)

CODEBLOCK3

Manually execute tasks

CODEBLOCK4

Check status

CODEBLOCK5

Stop monitoring

CODEBLOCK6

Execution Rules

1. 1. If .claude-status.txt does not exist or contains 0, start executing unfinished tasks from INLINECODE18
2. When executing tasks, set .claude-status.txt to INLINECODE20
3. When all tasks are completed, set .claude-status.txt to INLINECODE22
4. Scheduled task checks every 1 minute:

- If status = 0 or file doesn't exist + pending tasks = start execution - If status = 1 = Claude is running, continue waiting - If status = 2 = All tasks completed, exit monitoring

1. 5. Monitoring automatically exits when all tasks are completed (status=2)

Task Marking Format

In checklist.md, tasks use the following format:

• - [ ] indicates incomplete
• INLINECODE28 indicates completed

Example:
CODEBLOCK7

Notes

• - Scheduled monitoring is session-level, stops when the current terminal session ends
• For persistent monitoring, use system cron or launchd
• The SessionStart hook checks for checklist.md in the current working directory at runtime
• Configuration is project-local via INLINECODE30

Security Notes

What this skill accesses:

• - Reads checklist.md in your current project directory
• Creates/reads .claude-status.txt in your current project directory
• Writes execution log to INLINECODE33
• Does NOT access the internet
• Does NOT request or transmit credentials

What the installer modifies:

• - .claude/settings.local.json - Project-local settings (gitignored)
• INLINECODE35 - Project-local scripts

Persistence:

• - The SessionStart hook runs at the start of each Claude Code session in this project
• It only starts monitoring if checklist.md exists and no execution is in progress
• Uninstall removes all modifications in the project

How Task Execution Works

1. 1. The shell scripts (fullrun.sh, cron-manager.sh) handle:

- State management (.claude-status.txt) - Task queue management (reading checklist.md) - Logging (.fullrun.log) - Marking tasks as complete

1. 2. Task execution is delegated to Claude Code:

- When a task is started, it outputs the task description - Claude Code reads the task and executes the appropriate commands - This design allows for complex, multi-step tasks that require AI reasoning

Cross-Platform Compatibility

• - macOS: Fully supported
• Linux: Fully supported
• Windows: Requires WSL or Git Bash

The scripts use awk for text processing to ensure consistent behavior across all platforms.