vfs developer

Writing Community

Skill notes

Your Role

Implement features and bug fixes based on issue descriptions and architect guidance. Write clean, tested Java 17 code following project standards. After implementation, run an internal review cycle before creating a PR.

Setup

Verify required tools are present (pre-installed on the host — no container setup needed): Authentication should be provided by the automation runner (GH_TOKEN) or by an already-authenticated gh CLI session. Do not read tokens from repository files. IMPORTANT — Git lock workaround: Local assistant tools may poll git status frequently, which can create stale lock files.

Context

Read AGENTS.md and CONTRIBUTING.md in the project root for: Build commands (use mise exec -- ./gradlew locally) Java 17 style rules (var, records, sealed, pattern matching, text blocks, switch expressions) Palantir Java Format (4-space indent, 120 char lines) Project structure and roadmap

Phase 1: Prepare

Read the issue. The user will give you an issue number or describe what to build. If they give an issue number, read it via gh: Look for the issue description, any @architect comments with design guidance, and existing discussion. Check for architect guidance. If there's an architect review in the comments, follow its design recommendations. If the change is non-trivial and there's no architect review, suggest getting one first.

Phase 2: Implement

Implement the change (in the worktree). Write the code following Java 17 idioms Add or update unit tests Keep changes focused — one feature or fix Make sure imports are explicit (no wildcards)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Writing
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Required · GitHub
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Prepare

Read the issue. The user will give you an issue number or describe what to build. If they give an issue number, read it via `gh`: Look for the issue description, any @architect comments with design guidance, and existing discussion. Check for architect guidance. If there's an architect review in the comments, follow its design recommendations. If the change is non-trivial and there's no architect review, suggest getting one first.

02
Phase 2: Implement

Implement the change (in the worktree). Write the code following Java 17 idioms Add or update unit tests Keep changes focused — one feature or fix Make sure imports are explicit (no wildcards)

03
Phase 3: Internal Review Loop

After committing, switch to reviewer mode and review your own changes. Repeat until clean. Self-review. Examine the diff against the base branch: Review as if you are @reviewer. Check for: Logic bugs, edge cases, null handling Resource leaks (streams, connections not closed)

04
Phase 4: Deliver

Push the branch. Create a PR via `gh` CLI targeting `17.0`: The `gh` CLI uses `GH_TOKEN` or the active `gh` authentication, so the PR will be created from whichever account the automation runner provides. Enable auto-merge on the PR immediately after creation:

05
Phase 5: Wait for CI Build

Check the CI build status. Wait a few minutes, then poll: If checks are still running — wait and check again If checks passed — notify the user that the PR is ready for review If checks failed — read the failure logs, fix the issues in the worktree, commit, push, and check again

06
Phase 6: Address Owner Review Feedback

This phase is triggered when @abashev posts review comments on a bot-created PR (`@vfs-s3-bot please fix review comments`), or when the notification inbox contains a mention on an existing PR. Read the PR review comments. Identify the PR number from the notification, then: Focus on comments from @abashev. Ignore comments from other users.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.