simple pr

Engineering Community

Skill notes

Step 1: Check workspace state

Run: git status Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with git add. Also verify that we are on the main branch. If not, abort and ask the user to switch to main first.

Step 2: Ensure main is up to date

Run: git pull origin main This ensures we're working from the latest code.

Step 3: Review staged changes

Run: git diff --cached Review the staged changes to understand what the PR will contain.

Step 4: Generate commit message

Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what". Display the proposed commit message to the user and ask for confirmation before proceeding.

Step 5: Create a new branch

Get the git username: git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]' Create a short, descriptive branch name based on the changes (e.g., fix-typo-in-readme, add-retry-logic, update-deps). Create and checkout the branch: git checkout -b {username}/{short-descriptive-name}

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@quickwit-oss · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

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

01
Step 1: Check workspace state

Run: `git status` Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with `git add`. Also verify that we are on the `main` branch. If not, abort and ask the user to switch to main first.

02
Step 2: Ensure main is up to date

Run: `git pull origin main` This ensures we're working from the latest code.

03
Step 3: Review staged changes

Run: `git diff --cached` Review the staged changes to understand what the PR will contain.

04
Step 4: Generate commit message

Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what". Display the proposed commit message to the user and ask for confirmation before proceeding.

05
Step 5: Create a new branch

Get the git username: `git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'` Create a short, descriptive branch name based on the changes (e.g., `fix-typo-in-readme`, `add-retry-logic`, `update-deps`). Create and checkout the branch: `git checkout -b {username}/{short-descriptive-name}`

06
Step 6: Commit changes

Commit with the message from step 3:

07
Step 7: Push and open a PR

Push the branch and open a PR: Report the PR URL to the user when complete.

Discussion

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