What you get
- A technical specification of the task, written against your codebase, for your team to approve or correct.
- A pull request on your repository, with the spec, the test results and what the self-review and security scan found.
- A review call where we go through the pull request together and you decide what it is worth.
How it works
- You send one task with the form below.
- Intake call (30 minutes): we agree the scope and the acceptance criteria in writing, and you give access to one repository with a token you can revoke at any time.
- CodeLynq writes the specification. Your team approves it before any code is written.
- CodeLynq implements it, runs your tests, reviews and scans its own diff and opens a pull request.
- Review call (30 minutes): we go through the result. You merge it, change it or throw it away. Afterwards we remove our access.
Terms
- Scope: one task, roughly half a day to two days of work for one developer. A bug fix, a small feature or a refactor works well.
- Repository: one repository on GitHub, GitLab or Bitbucket, preferably with a test command we can run.
- Turnaround: a pull request within 5 working days after the specification is approved and we have access.
- Guidance: the intake and review calls are with the founder, and you can reach us during the run.
- Acceptance: the result is judged against the acceptance criteria agreed at the intake.
- Cost: free and without obligation. The code is yours, and nothing is merged by us.
Your team stays in control
CodeLynq never merges and never pushes to protected branches. Your team approves the specification, reviews the code and decides what goes in. How your code is handled, who has access and which subprocessors are involved is on our security page.
What you will get back
Worked example. Not a customer case: an illustration of the steps every run goes through.
1. Task
The request, as written
“Customers want to download their invoices as CSV from the invoice overview.”
2. Questions
Scope is settled before any code
CodeLynq asks what the request leaves open. Which columns? The filtered list or everything? Amounts with or without VAT? The product owner answers in the validation chat.
3. Specification
Your team approves the plan
A technical spec written against the real codebase: a GET /invoices/export.csv endpoint that respects the active filters, streams rows, is limited to the user's own organisation, and has tests for each. Nothing is built until someone approves it.
4. Implementation
Built on its own branch
4 files changed, +186 −3: the endpoint, a CSV writer, a download button and the tests.
5. Checks
Verified before a human looks
Your test command: 23 passed. Self-review found one issue and fixed it: cells starting with = could run as spreadsheet formulas. Security scan: no findings.
From the diff: what the self-review added · invoices/export.py def _cell(value) -> str:text = "" if value is None else str(value)+ # Spreadsheet apps run cells starting with = + - @ as formulas.+ if text[:1] in ("=", "+", "-", "@"):+ return "'" + textreturn text6. Pull request
Ready for your review
The PR links the approved spec and lists what was checked. Your developers review it like any other PR. CodeLynq never merges.
OpenAdd CSV export to the invoice overview+186 −3 · 4 files · tests passing · ready for review
Send us your task
Describe the task and the repository it belongs to. We reply within one working day to plan a short intake.
Rather talk first? Book a 30-minute demo.
After the challenge: a plan or a guided pilot
Want to keep going on your own? Choose a plan from €59 a month and connect your repositories yourself.
Rolling it out across several teams, or need SSO, compliance or self-hosted runners first? Then we set up a guided pilot together: several tasks, a fixed period and agreed success criteria.
Questions
- What happens to our source code?
- The run works on a copy of the one repository you give access to. The token is scoped and revocable, and we remove access after the review call. Code can be processed by the model provider of the coding agent; the security page lists who processes what and where.
- Which languages and frameworks work?
- Any repository the agent can build and test. Tell us your stack in the form and we will say at the intake whether the task is a good fit.
- What if the pull request is not good enough?
- Then you have learned that cheaply, and we want to hear why. You are under no obligation, and we will be honest about what CodeLynq does not do well yet.
- Do we have to buy anything afterwards?
- No. The challenge is free and without obligation.