open pr

AI Community

Skill notes

Step 1: Pre-flight checks

Before opening the PR: Ensure all changes are committed Ensure the branch is pushed to the remote (git push -u origin <branch>) Run linters/formatters across the whole repo (not just changed files) and commit any fixes

Step 2: Test coverage

This is critical. Before opening the PR, verify:

Existing behavior is not broken

Identify which modules/components your changes touch Run the existing test suites for those areas If tests fail, fix them before opening the PR — do not open a PR with known regressions

New behavior has test coverage

Every new feature, endpoint, or behavior change needs tests If you added a new block, add tests for that block If you changed API behavior, add or update API tests If you changed frontend behavior, verify it doesn't break existing flows If you cannot run the full test suite locally, note which tests you ran and which you couldn't in the test plan.

Step 3: Create the PR using the repo template

Read the canonical PR template at .github/PULL_REQUEST_TEMPLATE.md and use it verbatim as your PR body: Read the template: cat .github/PULL_REQUEST_TEMPLATE.md Preserve the exact section titles and formatting, including: ### Why / What / How ### Changes 🏗️

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
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
@Significant-Gravitas · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
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: Pre-flight checks

Before opening the PR: Ensure all changes are committed Ensure the branch is pushed to the remote (`git push -u origin <branch>`) Run linters/formatters across the whole repo (not just changed files) and commit any fixes

02
Step 2: Test coverage

This is critical. Before opening the PR, verify:

03
Step 3: Create the PR using the repo template

Read the canonical PR template at `.github/PULL_REQUEST_TEMPLATE.md` and use it verbatim as your PR body: Read the template: `cat .github/PULL_REQUEST_TEMPLATE.md` Preserve the exact section titles and formatting, including: `### Why / What / How` `### Changes 🏗️`

04
Step 4: Review workflow

Step 4: Review workflow

05
Step 5: Address review feedback

Once the review bot or human reviewers leave comments: Run `/pr-address` to address review comments. It will loop until CI is green and all comments are resolved. Do not merge without human approval.

06
Step 6: Post-creation

After the PR is created and review is triggered: Share the PR URL with the user If waiting on the review bot, let the user know the expected wait time (~30 min) Do not merge without human approval

Discussion

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