work-on
- Repo stars 2,483
- License MIT
- Author updated Live
- Author repo node-google-spreadsheet
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @theoephraim · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Bun
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: work-on
description: Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and cre…
category: engineering
runtime: Bun
---
# work-on output preview
## PART A: Task fit
- Use case: Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and create a PR You are given an issue or external PR to implement. The input may be a URL, pasted issue text, or pasted PR diff/description. makes outbound network calls; runs on Bun. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflow / 1. Understand the task / 2. Create a branch” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and create a PR You are given an issue or external PR to implement. The input may be a URL, pasted issue text, or pasted PR diff/description. makes outbound network calls; runs on Bun. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Workflow / 1. Understand the task / 2. Create a branch” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Workflow / 1. Understand the task / 2. Create a branch”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: work-on
description: Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and cre…
category: engineering
source: theoephraim/node-google-spreadsheet
---
# work-on
## When to use
- Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and create a PR You are given…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Workflow / 1. Understand the task / 2. Create a branch” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "work-on" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflow / 1. Understand the task / 2. Create a branch
rules -> SKILL.md triggers / order / output contract
runtime -> Bun | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}You are given an issue or external PR to implement. The input may be a URL, pasted issue text, or pasted PR diff/description.
Input: $ARGUMENTS
Workflow
Follow these steps in order:
1. Understand the task
- If given a URL, fetch it to read the issue/PR details.
- Analyze the issue or PR to understand what needs to be done.
- Summarize the task back to the user and confirm before proceeding.
2. Create a branch
- Create a descriptive branch name based on the task (e.g.,
fix/cell-formatting-bug,feat/add-batch-update). - Branch from
main.
3. Implement the changes
- Make the necessary code changes.
- Follow existing code patterns and conventions in the project.
4. Add or update tests
- Add tests for the new functionality or bug fix in
src/test/. - Follow existing test patterns — tests are integration tests that hit real Google APIs.
- If modifying existing behavior, update relevant existing tests as needed.
- To validate, only run the relevant test file(s) to avoid rate limiting:
bun vitest run src/test/<relevant-file>.test.ts - Do NOT run the full test suite.
5. Update documentation
- If your changes affect the public API (new methods, changed parameters, new features, etc.), update the relevant docs in
docs/.- Class API docs are in
docs/classes/(one file per class:google-spreadsheet.md,google-spreadsheet-worksheet.md,google-spreadsheet-row.md,google-spreadsheet-cell.md). - Guides are in
docs/guides/. - The sidebar is
docs/_sidebar.md— update it if adding a new page.
- Class API docs are in
- Match the style and format of the existing documentation.
6. Lint
- Run
bun run lint:fixto auto-fix any lint issues. - If lint errors remain, fix them manually.
7. Add a changeset
- Run
bun changeset— since this is interactive, instead create the changeset file directly. - Create a
.changeset/<descriptive-name>.mdfile with the appropriate format:--- "google-spreadsheet": <patch|minor|major> --- <Short description of the change> - Use
patchfor bug fixes,minorfor new features and non-breaking changes,majorfor breaking changes.
8. Commit and push
- Stage and commit all changes with a clear commit message.
- Push the branch to origin.
9. Create a PR
- Use
gh pr createto open a pull request. - Write a clear title and description summarizing the changes.
- If the input was a GitHub issue, reference it in the PR body (e.g., "Fixes #123").
- Return the PR URL to the user.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review